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.
Overview of the Issue
We were able to reproduce this issue running v0.24.3, v0.24.4 and v0.25.0.
We have a project structure similar to
test
├── atlantis.yaml
└── infra
├── modules
│ └── module-one
├── project-one
└── project-two
We change project-one/main.tf and atlantis runs the plan just for project-one.
If we update modules/module-one/some-file.tf and module-one is used only for project-two, then Atlantis runs the plan only for project-two.
But if we change, for example, project-one/README.md Atlantis also runs the plan for project-one although the updated file doesn't match with ATLANTIS_AUTOPLAN_FILE_LIST.
If we downgrade to v0.23.3, the previous version after this fix, then use case 3) works (i.e., Atlantis doesn't run anything wen we change files not matching ATLANTIS_AUTOPLAN_FILE_LIST), but Autoplan Modules (use case 2) stops working. So, I'd say it's a regression introduced by the linked PR.
Reproduction Steps
Just follow the two use cases I listed above.
Logs
Environment details
Additional Context
The text was updated successfully, but these errors were encountered:
Community Note
Overview of the Issue
We were able to reproduce this issue running v0.24.3, v0.24.4 and v0.25.0.
We have a project structure similar to
test ├── atlantis.yaml └── infra ├── modules │ └── module-one ├── project-one └── project-two
and our
atlantis.yaml
file looks likeAtlantis is running with the following environment variables
Everything works as expected, i.e.,
project-one/main.tf
and atlantis runs the plan just forproject-one
.modules/module-one/some-file.tf
andmodule-one
is used only forproject-two
, then Atlantis runs the plan only forproject-two
.project-one/README.md
Atlantis also runs the plan forproject-one
although the updated file doesn't match withATLANTIS_AUTOPLAN_FILE_LIST
.If we downgrade to v0.23.3, the previous version after this fix, then use case 3) works (i.e., Atlantis doesn't run anything wen we change files not matching
ATLANTIS_AUTOPLAN_FILE_LIST
), but Autoplan Modules (use case 2) stops working. So, I'd say it's a regression introduced by the linked PR.Reproduction Steps
Just follow the two use cases I listed above.
Logs
Environment details
Additional Context
The text was updated successfully, but these errors were encountered: