executable_name, config name etc?

We aren't using those at the moment, would those change this at all?

Is executable name going to change that component?

Because we don't really worry too much about the actual atlantis commands, it's the status checks that's the issue atm.

I should take that back, we're using the config name thing so we can have separate config files, but not changing the executable name atm.

Hrm. Actually, is this something that can be solved with ATLANTIS_SILENCE_VCS_STATUS_NO_PLANS? If we can just have atlantis-nonprod not give any status check for prod changes, for instance, that would be fine, the problem now is that it will just sign off on prod changes because nothing is changing.

the idea of the atlantis executable is that when you do

atlantis-prod plan

only the prod atlantis response back, the rest will discard the command

and options like this : ATLANTIS_SILENCE_VCS_STATUS_NO_PLANS will help with the noise

silence-no-projects too etc

That's the thing I'm wondering if ATLANTIS_SILENCE_VCS_STATUS_NO_PLANS will fix

you will have to test it , I do not remember

Thanks!