ci-cd: rename release to deploy

Azure / devops-governance

Example end-to-end Governance Model from CI/CD to Azure Resource Manager. Use this project to deploy example AAD, ARM and Azure DevOps resources to learn about e2e RBAC.

MIT License

189 stars 93 forks source link

ci-cd: rename release to deploy #10

Closed julie-ng closed 3 years ago

julie-ng commented 3 years ago

Trigger deployment, testing re-configuration of branch protection rules.
Merging changes from #9

azure-pipelines[bot] commented 3 years ago

⚠️ Configuration Drift Detected

Source Version: 61359e5b1b4fd2596b5fa817b27fb1323d6a62d4

Approving this Pull Request may result in destructive changes to your Azure resources. Please review the terraform plan output diff at Azure Pipelines Build Result Page.

Proceed with caution!

azure-pipelines[bot] commented 3 years ago

🟢 No configuration drift detected

Source Version: 61359e5b1b4fd2596b5fa817b27fb1323d6a62d4

julie-ng commented 3 years ago

All the back and forth builds have to do with re-setting up all pipelines and branch protection permissions after moving repository from azure-samples to azure org.
TIL the PR triggered build runs are tied to the event not the git sha.