Closed seidzade closed 1 month ago
Did more tests , update - if "plan_requirements: [approved]" is set - the prevention works only on initial flow . If executed manually , by PR comment - ignored also
initial comment
As I said in initial post , one of the suspicions was a Azure repo URL naming convention style - xxx.visualstudio.com/xxx/DevOps/devops.iac OR dev.azure.com/xxx/DevOps/devops.iac
So , tried following config , and prevention works (2 configs for same repo but different URLs)-
repos:
- id: xxx.visualstudio.com/xxx/DevOps/devops.iac
workflow: default
allowed_workflows: [default]
apply_requirements: [approved]
branch: /master/
autodiscover:
mode: auto
pre_workflow_hooks:
- run: |
...
...
...
post_workflow_hooks:
- run: |
...
...
...
- id: dev.azure.com/xxx/DevOps/devops.iac
workflow: default
allowed_workflows: [default]
apply_requirements: [approved]
branch: /master/
autodiscover:
mode: auto
workflows:
default:
plan:
steps:
...
...
...
Did it like this because have troubles to receive some vars for "pre"/"post"/"workflow" steps in case of "id: dev.azure.com/xxx/DevOps/devops.iac" (bug???) , have no idea why , will debug it later .. Normal config should not duplicate repos config , of course
So , I think that it worth to update documentation on that case for Azure configuration requirements, it's not straight forward to understand such a dependency . Thanks all for the work :)
Community Note
Overview of the Issue
Azure Devops , Atlantis deployed in AKS cluster using stateful set , the "apply_requirements [approved]" settings defined as part of official helm chart values.yml, and being ignored. At the same time , "plan_requirements [approved]" - works
Server side single repo config only.
Reproduction Steps
Logs
Environment details
Atlantis server-side config file:
Additional Context
For me its looks like very similar to #3270 , but for case of Azure Devops My suspicions: