This message was deleted.
# atlantis-community
s
This message was deleted.
g
You can mange it via different roles via specification in cloud provider if we are talking about aws for example.
j
are theses PRs all from the same repo?
c
No. every project have there own repo and owned by a team i rather not do it via provider as that then could be bypassed by the team
j
then i'd run multiple Atlantis instances with different repo whitelistings
☝️ 1
c
That's really the only option if you want to make sure that Atlantis can't do what you're asking.
c
then we where no so off thinking thats our only option. Thanxs 👍
🙌 1
t
You can try to do a custom workflow for each project and use pre_hook to set up correct credentials if i understood your request correctly
👍 1
c
Where thinking if we could do it and dynamic with variables
m
I think that you can try use direnv
you can use .envrc to set diferentes environments variables to each project/repository
then you can use something like it :
Copy code
- run: direnv exec . terraform plan -input=false -out=$PLANFILE
in the workflow
o
@Christoffer Nicklasson finally did you try out anything other than aws_profiles in providers. ?
c
been on vacation , so haven't got time to test