You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
multienv is powerful for configuration within workflows, but when used has the disadvantage of reducing visibility that Atlantis provides by outputting redundant information.
Describe the drawbacks of your solution
I can't think of any drawbacks, as this would be opt-in and someone using it should be aware of the loss of contextual information from multienv.
Describe alternatives you've considered
Using a standard env instead with output disabled, however that defeats the flexibility of the multienv directive.
Implementing a toggle like output: hide, which is used in run directives, instead of an environment variable toggle.
The text was updated successfully, but these errors were encountered:
Community Note
Describe the user story
As an end-user of Atlantis, when
multienv
is used, I don't want to see this output.Describe the solution you'd like
Environment variable to disable
multienv
output, e.g.ATLANTIS_MULTIENV_OUTPUT
.This would suppress the following output when Atlantis runs a plan/apply:
multienv
is powerful for configuration within workflows, but when used has the disadvantage of reducing visibility that Atlantis provides by outputting redundant information.Describe the drawbacks of your solution
I can't think of any drawbacks, as this would be opt-in and someone using it should be aware of the loss of contextual information from
multienv
.Describe alternatives you've considered
env
instead with output disabled, however that defeats the flexibility of themultienv
directive.output: hide
, which is used inrun
directives, instead of an environment variable toggle.The text was updated successfully, but these errors were encountered: