This message was deleted.
# atlantis-community
s
This message was deleted.
r
what are you trying to achieve? different policies for different repos?
j
No, I just need to be able to tell all the projects in this mono repo, to use the same, remote, conf test
This reads like to use remote policies, we would need to define it for each project.
r
ah, i see. are you using multiple/custom workflows and/or parallel plans?
j
I do not believe so.
Def, not using any custom workflows, I would hope atlantis does parallel plans by default
The only configuraiton in place, is this
Copy code
repoConfig: |
 ---
 repos:
 - id: /.*/
   apply_requirements: [mergeable]
   import_requirements: [mergeable]
r
in that case, you can add the statement as shown to the default workflow and it will work. in the case of enabling parallel_plans, there is an issue we ran into where there is contention on the directory which is being updated, where one policy check goes to update the policy dir while another goes to run checks. some policies may go missing in that window, causing errors. for our case, we wrapped the update command into a script which gets executed in a run step prior to
policy_check
, and uses
flock
to ensure only one policy operation is happening at the same time as an upgrade.
j
hmm, so it doesnt read like this is even enabled by default
Copy code
parallel_plan: true
parallel_apply: true
r
if that's in your atlantis.yaml, then parallel plans and applies are enabled. but by default they are not enabled
j
we do not have atlantis.yaml files
really strange you can just enable it by default, creating atlantis.yaml files for a mono repo is a PITA
since its constnatly changing
r
i'm not sure i follow. strange to enable parallel operations by default?
j
Its strange that I can not define it as being enabled in the server config
instread of having to maintain an atlantis.yaml file, and defining every single project in this ever changing monorepo
r
i have a PR up to allow this
🙌 1