This message was deleted.
# atlantis-community
s
This message was deleted.
d
Hello, it really depends on your terraform repository structure. How do you have your environments separated? Some people separate them with workspaces or separate folders/projects, other setup completely separate Atlantis instances
s
I have a single TF repo for all environments and a single Atlantis instance that can assume roles in the other accounts (almost everything is AWS)
d
What is the folder structure like? I'm assuming you have different folders for the environments. Check out: https://www.runatlantis.io/docs/repo-level-atlantis-yaml.html#requiring-approvals-for-production
you can setup requirements to be stricter about prod versus dev/stage
s
infra/environments/{dev,prod,etc}/{various,components}
we were using approved PRs are required for apply across every environment, but I've changed that so that approval isn't required in non-prod environments with the idea that the PR author will apply to non-prod envs prior to asking for review / approval to apply to prod, which I think is reasonable, we'll see how it works
d
Yup exactly. Meragable is usually more powerful than approved especially with the GH backend and branch protections
c
I think it's worth interrogating why they are worried about Atlantis applying against your infra but not a random person....