[Feature Request] Allow force flag for az repos policy create
See original GitHub issueIs your feature request related to a problem? Please describe.
If the branch policy already exists, we will need to use az repos policy update
command. This means I need to first get the policy id. Getting the policy id for a repo is not intuitive especially because az repos policy list
lists just repository id
Describe the solution you’d like
Allow me to set the --force
flag for az repos policy create
command
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Git branch policies and settings - Azure Repos - Microsoft Learn
To set branch policies, you must be a member of the Project Administrators security group or have repository-level Edit policies permissions ...
Read more >Configuration Options - Renovate Docs
This feature allows you to use Renovate's Dependency Dashboard to force approval of updates before they are created. By setting dependencyDashboardApproval ...
Read more >Manage issues - GitLab Docs
Be careful when moving an issue to a project with different access rules. ... To make it available, ask an administrator to enable...
Read more >Securing Git Branches through Azure DevOps CLI
... defined as bit flags. The following shows the "Git Repositories" security namespace: ? az devops security permission namespace list `.
Read more >Deploying Docker containers on Azure
For example, let us create a new context called myacicontext : ... To remove a running container, you must use the --force flag,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@onlyutkarsh - Let me look into this. I did a quick check and the ID remains the same even after 10 minutes of change. I will loop in the team as well to try and repro this. Will keep you posted on progress.
Including scenario context: We have close to 50+ repos and new ones getting created each day. Apart from “required reviewer” and “build validation” policy types (which change per repo), I would like to keep following (4 below) policies same and in sync for all repos. I would like to run this using az devops cli as part of scheduled pipeline.
This will ensure, even if policy is changed by someone manually, the pipeline will re-apply them in next run. Hope that makes sense.