Set "default" workspace in a repo.yaml

[mbarr-hrp]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

---

• I'd be willing to implement this feature (contributing guide)

Describe the user story
As a infra owner, I'd like to set the default workspace for an Atlantis instance.

The goal is to run multiple servers, and each have their own workspace set.

Describe the solution you'd like
I'd like to be able to set a default workspace to be something other than "default".

It could be in ENV flag, cli option, or repo.yaml file. (Atlantis.yaml would be far less ideal, unless it's on top level, not a per-project basis.)

Describe the drawbacks of your solution
None, other than slight complexity to the default code.

Describe alternatives you've considered
I've added a custom default workflow to specify the workspace in the command, but that means that the comments still say the workspace is "default", and the paths are set to use "default" as the file checkout location for the plan, and the name of the plan is default.yaml.

(It works, but it's confusing to the users.)

I've looked through the various docs, and posts and issues, and haven't found a way to set the workspace to be anything other than default as a high level override.

[mbarr-hrp]

It looks like this may be related to an conversation that @jskrill & @nitrocode had, referencing.

This next bit may be better as a separate feature, but:

I also want to also be able to scope what directories are listened to for auto-discovery.

Basically, we have a mono repo, w/ TF code & app code seperated.
a-e are separate accounts w/ separate workspaces.

| - App1 (a)
|   * project 1-N
| - Big App (b,c,d)
|   * project 1-N
| - App2 (e)
|   * project 1-N

I want to have

• 1 server look at App1
• 3 servers look at the Big App, w/ it's progression, each their own account/credentials / workspaces.
• 1 server look at App2.

I think it could be implemented as either a repo or an atlantis.yaml feature, similar to what was proposed by @nitrocode.

• A default (workspace) for all projects, or just auto discovered ones.
• an allow list for directories for auto-discovery.

Happy to talk on Slack if it helps, and I might even be able to get some team members that are better at go to help implement, if we can get a preferred solution.