Atlantis

No, what you will want to do instead is isolate projects to the individual 2 servers for now so they don't conflict

<https://www.runatlantis.io/docs/server-configuration.html#executable-name>

<https://www.runatlantis.io/docs/server-configuration.html#silence-no-projects>

<https://www.runatlantis.io/docs/server-configuration.html#vcs-status-name>

with all those you can have multiple atlantis servers from one repo

search for `multiple Atlantis` in the docs

<https://www.runatlantis.io/docs/server-side-repo-config.html#multiple-atlantis-servers-handle-the-same-repository>

<@U0144ERR2QP> I have tried the `@staging-atlantis-server plan` and nothing moved (not even in the logs of the corresponding server; Any suggestions about what might be missing? Using `atlantis 0.23.4`

Screenshot 2023-05-02 at 9.46.51 PM.png

yes. I just logged in however with that user and i don’t see it having been mentioned so perhaps the issue for the moment is on on the `atlantis` side :thinking_face:

i am using
```@my-actual-github-handle-of-atlantis-server plan```

This is the user whose PAT is being used to communicate with gh from the particular server

you should see something in the logs at least

after you change that and resart atlantis it should parse the new executable name

I didn’t realise you should rename the executable…

this should also work with both the `plan`/ `apply` verbs, right?

Screenshot 2023-05-03 at 6.49.44 PM.png

I was not setting that flag so proceeding…