Repository navigation
Treat the always-applied default profile in AWS repositories as intended - #3375
Merged
ryanjbaxter merged 1 commit intoNov 2, 2026
Merged
Conversation
The AWS Secrets Manager and Parameter Store repositories apply the default profile even when another profile is active, so that application-default is shared by every profile. This is documented, so keep the behavior instead of changing it. Add a DEFAULT_PROFILE_ALWAYS_ACTIVE capability to the compliance tests. Repositories that declare it skip the scenario expecting Spring Boot's behavior and run a scenario that pins the documented behavior instead. Signed-off-by: Ryan Baxter <ryan.baxter@broadcom.com>
spencergibb
approved these changes
Nov 2, 2026
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
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.
The AWS Secrets Manager and Parameter Store repositories apply the default profile even when another profile is active, so that application-default is shared by every profile. This is documented, so keep the behavior instead of changing it.
Add a DEFAULT_PROFILE_ALWAYS_ACTIVE capability to the compliance tests. Repositories that declare it skip the scenario expecting Spring Boot's behavior and run a scenario that pins the documented behavior instead.