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.
My expected behavior is running workflows default and custom-workflow to do policy check for custom-project with everything fine.But I got some issues:
I set an environment variable ENV_VAR_TEST in workflow default and also have the policy check env-variable-check in this workflow but not custom-workflow, but I got error info print from policy check env-variable-check when I run atlantis plan. The policy check can be success if I remove the custom-workflow.
I have tried to write as following with multiple policy checks:
Community Note
Overview of the Issue
Say I have the config
repos.yaml
as following:And
atlantis.yaml
as following:My expected behavior is running workflows
default
andcustom-workflow
to do policy check forcustom-project
with everything fine.But I got some issues:ENV_VAR_TEST
in workflowdefault
and also have the policy checkenv-variable-check
in this workflow but notcustom-workflow
, but I got error info print from policy checkenv-variable-check
when I runatlantis plan
. The policy check can be success if I remove thecustom-workflow
.But only last one policy check will be run with above format.
Any suggestions will be appreciate.
Reproduction Steps
Logs
Environment details
Additional Context
The text was updated successfully, but these errors were encountered: