Feature request: flag to disable plan/apply on projects not included in atlantis.yaml

[grace-hunter]

We have a monorepo and would like to have a separate Atlantis instance per environment (stage, prod, etc).

So far, we've accomplished this by generating a different atlantis.yaml on each Atlantis server via a pre-workflow hook.
The --silence-no-projects and --silence-vcs-status-no-plans flags are set, so only the appropriate Atlantis server responds responds to each request. This works nicely for autoplanning and regular atlantis plan/atlantis apply.

When you run atlantis plan -d <dir>, however, all of the Atlantis instances respond, so you get one correct plan and then several unwanted plans that (in our case) fail. If you subsequently run atlantis apply -d <dir>, you get one correct apply result and several No plan found comments.

If there was an option to only allow plan/apply to run on projects listed in atlantis.yaml and skip everything else, I think that would solve this problem. Alternatively, if anyone else has an existing workaround please let me know!

[spuder]

We are also running multiple atlantis servers because we are on-prem and have hard network segmentation limits.
We are doing the same thing where we have dynamically generated atlantis.yaml files so only the production atlantis runs production terraform.

atlantis server --repo-config=/local/repos.yaml --silence-no-projects --silence-vcs-status-no-plans

/local/repos.yaml

#!/bin/bash
set -u
ATLANTIS_ENV=$1
cat >atlantis.yaml <<- EOF
version: 3
automerge: false
projects:
- name: consul-${ATLANTIS_ENV}
  dir: consul/${ATLANTIS_ENV}
  workspace: default
  autoplan:
    enabled: true
    when_modified: ["*.tf"]
- name: nomad-${ATLANTIS_ENV}
  dir: nomad/${ATLANTIS_ENV}
  workspace: default
  autoplan:
    enabled: true
    when_modified: ["*.tf"]
EOF
cat atlantis.yaml

However we also find that when doing atlantis plan -p <environment> that the non-acting atlantis server spits out a superfluous error. We haven't found a workaround yet.

It seems like --silence-no-projects should be hiding these messages. But we have that configured on all atlantis servers with no change in behavior.

--silence-no-projects will tell Atlantis to ignore PRs if none of the modified files are part of a project defined in the atlantis.yaml file.
This is useful when running multiple Atlantis servers against a single repository so you can delegate work to each Atlantis server. Also useful when used with pre_workflow_hooks to dynamically generate an atlantis.yaml file.

https://www.runatlantis.io/docs/server-configuration.html#flags

For reference, here is the MR where --silence-no-projects was added #1469

[jamengual]

is this still happening with v0.19.8?

[jstadnik]

With atlantis v0.20.0 this seems to still be the case.

[kemv]

Any updates on this ?

[nitrocode]

Sounds like we need a contributor who will expand the --silence-no-projects flag to prevent the pr comment mentioned by @spuder . We're always looking for contributors @kemv . Please feel free to propose a pr to resolve this.