How to run atlantis plan on a particular atlantis server?

[moloarte]

Hello,

Could I somehow use atlantis plan -d project1/service and somehow target the atlantis server I want this to run on?

I have a case, where multiple Atlantis servers will be used in one repository and even terragrunt is involved.
But with this particular case, I have the following directory structure:

project1
├── service
    ├── config
    │   └── development.yaml
    │   └── production.yaml
    ├── main.tf
    ├── vars.tf
    ├── outputs.tf
    └── terragrunt.hcl

Inside every project, there is a directory with a configuration file for each environment. Before running terragrunt I define a parameter that defines which will be used to target the environment in which I want to make a change.

Even without testing, I know that atlantis plan will trigger all servers unless I have a way to tell them not to react to a certain event.

Thanks in advance!

[jamengual]

look at this :

#2798
#1345 (comment)
https://www.runatlantis.io/docs/server-configuration.html#enable-regexp-cmd

[moloarte]

I set up the configuration as the example suggests. However, I was not able to dynamically modify the atlantis.yaml to point to the directory I want to target.

version: 3
delete_source_branch_on_merge: true
projects:
  - name: dev
    dir: .
    autoplan:
      when_modified: [ "base/**/config/dev.json",
                       "addons/**/config/dev.json",
                       "projects/**/config/dev.json" ]

of course, atlantis wants to run on . which is the top-level directory.

[moloarte]

I am thinking if there will be such a feature like atlantis plan -d $dir -l env=dev, where l stands for label, then we would be able to target a server better.
Again, this case might be too specific for it to be considered :)

[jamengual]

you can target projects base on regex and you can target branches too.
if you do it project base then you can have a bench per environment to push stuff through and in that case set the VCS name and those other flags to make it so all the servers receive the webhook event but only one responded.

Targetting a specific server with autoplan is hard impossible, targeting a server with a project it is easier.

And remember that we have pre-workflowhooks to do the atlantis.yaml generation on the fly and you can run a script or something to find the label and discard the label depending on which server you are etc.

you ill have to be crafty.

[moloarte]

I think I just solved my issue without the need of manipulating or generating the atlantis.yaml file.

The issue #2805 came to my attention and it turns out that the executable-name is an undocumented parameter in the application. Felt like finding gold.

So my solution is a combination of:

• custom executable-name
• custom vcs-status-name
• custom workflow for terragrunt

If acceptable, I could contribute in the documentation of this variable.

[jamengual]

mmm I thought we had docs for it? but I could be wrong and we will definitely love to have better docs so please go ahead.

…

On Fri, Apr 7, 2023, 8:37 a.m. M. Oloarte ***@***.***> wrote: I think I just solved my issue without the need of manipulating or generating the atlantis.yaml file. The issue #2805 <#2805> came to my attention and it turns out that the executable-name is an undocumented parameter in the application. Felt like finding gold. So my solution is a combination of: - custom executable-name - custom vcs-status-name - custom workflow for terragrunt If acceptable, I could contribute in the documentation of this variable. — Reply to this email directly, view it on GitHub <#3295 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQ3ERAXXOKCLS5X2657OH3XAAYELANCNFSM6AAAAAAWTNDZNM> . You are receiving this because you commented.Message ID: ***@***.***>