Fix an issue with the component_info output from the atmos describe component command. Add assume_role property to Atmos JSON Schema S3 backend
#621
Conversation
This file contains 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
…ons-1 # Conflicts: # examples/quick-start/Dockerfile # website/docs/integrations/atlantis.mdx # website/docs/integrations/github-actions/setup-atmos.md
osterman
approved these changes
Jun 8, 2024
|
These changes were released in v1.79.0. |
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.
what
component_infooutput from theatmos describe componentcommandassume_roleproperty to Atmos JSON Schema S3 backendwhy
The issue with the
component_infooutput from theatmos describe componentcommand was introduced in the previous PRs (different order of execution when evaluationGotemplates in Atmos stack manifests)Support the recommended
assume_roleproperty in S3 backends. Assuming an IAM Role can be configured in two ways. The preferred way is to use the argumentassume_role, the other, which is deprecated, is with arguments at the top level (e.g.role_arn)references