chore: make AWS compose env optional#32
Merged
Merged
Conversation
pantierra
force-pushed
the
chore/optional-aws-env
branch
from
July 2, 2026 14:16
e44edfe to
8788450
Compare
hrodmn
approved these changes
Jul 6, 2026
pantierra
force-pushed
the
chore/optional-aws-env
branch
from
July 6, 2026 14:38
8788450 to
7091e31
Compare
pantierra
enabled auto-merge (squash)
July 6, 2026 14:38
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
2 participants
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.
Pass AWS credentials through only when they are set so local compose validation does not warn for the default public-data workflow.
This removes a misleading warning that might confuse workshop participants.