Hide documentation banner for configuring Lambda functions when tool is hosted by Aspire #1951
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…is hosted by Aspire
normj
added
the
Release Not Needed
ghost
approved these changes
Jan 29, 2025
ghost
approved these changes
Jan 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes:
The banner on the home page explaining how to set the environment variable for lambda runtime API doesn't make sense when used from Aspire because Aspire takes care of all of that setup. This PR adds a utility method that detects when the tool is hosted by an Aspire and then uses that to hide the banner.
This commit in the Aspire repo is where the environment variable is set. aws/integrations-on-dotnet-aspire-for-aws@f12a0a0
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.