Is there a way to disable applying by directory?

[jrouly]

we've recently started generating atlantis.yaml dynamically on the server in a pre-workflow hook. this works great! it's allowed us to disable autoplanning for certain kinds of projects, and remove some projects from Atlantis altogether!

However, if the source code still exists in the repo, Atlantis can always be invoked with -d and a source directory. Is there any way to disable directory based application? Or, put another way, to enforce that atlantis.yaml is the source of truth for Atlantis' project support?

[jamengual]

mmm I do not think there is a way to disable that feature.

maybe you can hack a regex that does not match anything maybe? https://www.runatlantis.io/docs/server-configuration.html#enable-regexp-cmd

[jrouly]

Hmm that's not quite what I want -- it looks like that just influences the behavior of -p. Per the docs:

This will not work with -d yet and to use -p the repo projects must be defined in the repo atlantis.yaml file.

I like -p how it is because I'm already using an autogenerated atlantis.yaml file which restricts -p's targeting behavior. It's -d that's opening a troublesome backdoor.

[jamengual]

ahhhh yes, this does not work with -d my bad.

…

On Wed, Jan 24, 2024 at 1:36 PM Michel Rouly ***@***.***> wrote: Hmm that's not quite what I want -- it looks like that just influences the behavior of -p. Per the docs: This will not work with -d yet and to use -p the repo projects must be defined in the repo atlantis.yaml file. I like -p how it is because I'm already using an autogenerated atlantis.yaml file. It's -d that's opening a troublesome backdoor. — Reply to this email directly, view it on GitHub <#4173 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQ3ERDUBTPQAQVNBCJ3SIDYQF5GFAVCNFSM6AAAAABCJNHSUKVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DEMZXHEZDE> . You are receiving this because you commented.Message ID: ***@***.***>