data-management-zone
data-management-zone copied to clipboard
Updated Workflows
Summary of the Pull Request
- Fully switched to Bicep deployments
- Added deployment names
- Trigger on main only
- Changed what-if step in GH workflow
- Updated links to code of conduct
References
- Open issue in Data Management Zone: https://github.com/Azure/data-management-zone/issues/249
PR Checklist
- [x] Closes Issue https://github.com/Azure/data-management-zone/issues/249
- [x] CLA signed. If not, go over here and sign the CLA
Validation Steps Performed
See automated checks below.
I have changed my template to use AZURE CLI, I probably will be making a PR once I finish splitting it up for DEV,TEST,PROD https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/add-template-to-azure-pipelines?tabs=CLI
Just doing some testing and making sure I like the new design I am using.
- task: AzureCLI@2
inputs:
azureSubscription: $(azureServiceConnection)
scriptType: bash
scriptLocation: inlineScript
inlineScript: |
az account set `
--subscription ${{ parameters.AZURE_SUBSCRIPTION_ID }}
az deployment sub `
--location ${{ parameters.AZURE_LOCATION }} `
--subscription ${{ parameters.AZURE_SUBSCRIPTION_ID }} `
--template-file "$(System.DefaultWorkingDirectory)/infra/main.bicep" `
--parameters "$(System.DefaultWorkingDirectory)/infra/params.${{ parameters.environment }}.json"
@marvinbuss any idea when this workflow is getting merged in main?