Skip to content

Resolve S3 labels one after another - #3383

Merged
ryanjbaxter merged 1 commit into
spring-cloud:mainfrom
sharanggupta:gh-s3-compliance-labels
Nov 6, 2026
Merged

ryanjbaxter merged 1 commit into
spring-cloud:mainfrom
sharanggupta:gh-s3-compliance-labels

Conversation

@sharanggupta

Copy link
Copy Markdown
Contributor

With multiple labels, the S3 repository added the profile-specific files of every label before any file without a profile, so v1/orders-dev took precedence over v2/orders. This resolves each label completely before the next one, as the other repositories do, and enables the two disabled S3 compliance tests (profile expressions already pass).

With multiple labels the S3 repository added the profile-specific files
of every label before the files without a profile, so an earlier label
could override a later one. Resolve each label completely before the
next, as the other repositories do, and enable the S3 compliance tests
for multiple labels and profile expressions.

Signed-off-by: Sharang Gupta <sharang@sharanggupta.dev>
@github-project-automation github-project-automation Bot moved this to Todo in 2026.0.0 Nov 6, 2026
@ryanjbaxter ryanjbaxter added this to the 5.1.0 milestone Nov 6, 2026
@ryanjbaxter
ryanjbaxter merged commit 184de3f into spring-cloud:main Nov 6, 2026
2 checks passed
@github-project-automation github-project-automation Bot moved this from Todo to Done in 2026.0.0 Nov 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants