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
I have found that atlantis might confuse user what will be applied. In scenario when for other project verification I will run atlantis plan -d another_dir then atlantis will also apply those changes when running atlantis apply - it might be misleading, because when I run again atlantis plan then possible changes from another_dir are not included.
Also I would like to discuss that some sort of .atlantisignore file might be nice feature to have - prevent from applying on de/null-2. #26
Reproduction Steps
atlantis planatlantis plan -d another_diratlantis planatlantis apply
Logs
changes from autoplan, followed by custom plan -d
difference between projects default planned and applied
m00lecule
changed the title
atlantis run plan and apply on different projects -also ignores directories not listed in atlantis.yaml
atlantis run plan and apply on different projects - applies on directories not listed in atlantis.yaml
Nov 19, 2021
Overview of the Issue
I have found that atlantis might confuse user what will be applied. In scenario when for other project verification I will run
atlantis plan -d another_dir
then atlantis will also apply those changes when runningatlantis apply
- it might be misleading, because when I run againatlantis plan
then possible changes fromanother_dir
are not included.Also I would like to discuss that some sort of
.atlantisignore
file might be nice feature to have - prevent from applying onde/null-2
. #26Reproduction Steps
Logs
changes from autoplan, followed by custom
plan -d
difference between projects default planned and applied
Environment details
atlantis
0.17.5
Repo
atlantis.yaml
file:Additional Context
The text was updated successfully, but these errors were encountered: