0.23.5 attempts to autoplan a project even when autoplan is disabled. #3368
Labels
bug
Something isn't working
never-stale
regression
Bug introduced in a new version
Stale
waiting-on-response
Waiting for a response from the user
Community Note
Overview of the Issue
We just updated from 0.19.3 to 0.23.5, and a PR that changed two projects tried to make a plan for both, when the configuration indicates only one should autoplan.
Reproduction Steps
Open a PR with this config and changes to both directories, and see 2 plans instead of 1. (Except the project that should not plan is failing, which is why it is disabled.)
Here's a config. For
$REASONS
, theno-plan
project is disabled but present in ouratlantis.yaml
:Logs
The logs indicate the
when_modified
is the reason why both were planned:Environment details
atlantis server --atlantis-url=https://REDACTED --gh-user=REDACTED --gh-org= --repo-whitelist=github.com/REDACTED/* --repo-config=/home/atlantis/repos.yaml --config=/home/atlantis/config.yaml --default-tf-version=1.3.6 --hide-prev-plan-comments --allow-fork-prs --checkout-strategy=merge --log-level=info --enable-regexp-cmd --enable-diff-markdown-format
Atlantis server-side config files:
config.yaml
:(relevant parts of)
repos.yaml
:Repo
atlantis.yaml
file:see above
Additional Context
None
The text was updated successfully, but these errors were encountered: