Azure DevOps

Ever spent too much time debugging an issue that seemed impossible at first, but then turned out to be stupid? I have. Pipeline I was working on a pipeline. Just your run of the mill deployment pipeline really. I was trying to deploy some resources from a bicep template. It looked something like the following: variables: path: $(Build.SourcesDirectory)/agw-bicep agwName: 'my-agw' agwRg: 'my-agw-rg' kvName: 'my-agw-kv' trigger: none pool: vmImage: ubuntu-latest jobs: - job: deploy pool: vmImage: ubuntu-latest timeoutInMinutes: 15 steps: - task: AzureCLI@2 displayName: 'Call Azure Cli' inputs: azureSubscription: '<sub>' scriptType: 'pscore' scriptLocation: 'inlineScript' workingDirectory: $(oath) inlineScript: | (....

Secret Scanning in Azure DevOps with GitLeaks As you might know, it is important to keep any private keys, passwords and/or other secrets away from your source control. Having secrets in source control poses many risks, the most important one being: you have no idea how or where those secrets will be stored once someone pulls your repository. If your repository is private, then you might argue that it is reasonably safe, but even then secrets will be stored in plain text on the pc of every person that works with the repository....