When you use Azure DevOps to deploy your projects you can connect it to Azure via different methods. The most convenient type of service connection is `Azure Resource Manager using service principal authentication`.
This type of connection creates application in your Azure Active Directory which is used as a Service Principal. Then for this application secret is generated, so Azure DevOps can connect to Azure. This secret token is expiring from time to time. The default time to live is 2 years but it may vary.
Once the secret is expired you will get this type of error when trying to deploy your code to Azure:
##[error]Error: Failed to get resource ID for resource type 'Microsoft.Web/Sites' and resource name 'XXX'. Error: Could not fetch access token for Azure. Verify if the Service Principal used is valid and not expired. For more information refer https://aka.ms/azureappservicedeploytsg
Go to your SendGrid account and go to API Keys section.
Add new API Key with, at least, Mail Send permission.
Copy generated API Key. Your key should start with SG.
You have to edit Grafana configuration. Refer to Grafana Configuration documentation on where to find your config file. For Bitnami Grafana distribution you can find it here: /opt/bitnami/grafana/conf/grafana.ini
Look for [smtp] section and either update existing one or add new one
If you have Azure Log Analytics or Application Insights, where you have different data sources, like exceptions, requests, traces, customEvents, you may want to search for some certain phrase everywhere, because you don’t know in which data source you should check or in which column.
There is quite handy way of doing that – search in query.
search in (exceptions, requests, traces, customEvents) "ManagedIdentityCredential"
Adding a tag to your build in Azure DevOps is very useful – you can use it later on with releases to accept only builds with certain tags. That comes in handy when you are building a project with many different configurations which you will, later on, deploy via different releases. For example:
You can use it on client basis or environment basis like dev, uat, prod.
You can add as tag whatever you want. For example variable value that you can set, when you are starting the build. You can skip next step if you want to use existing variable in your pipeline.
Create variable in your build pipeline
Create or edit your existing pipeline.
Go to Variables/Pipeline variables tab.
Add your variable, for example EnvironmentTag and add default value.
Select Settable at queue time to make sure that you can change it when you are scheduling your build.
Add a stage to tag your build
Go to the Tasks tab.
It’s good to have 2 stages – one to perform all the tasks related to your build and the other to tag the build.
Add PowerShell or Bash task that will add tag based on EnvironmentTag variable value: Write-Host "##vso[build.addbuildtag]$(EnvironmentTag)"
When you go to the build pipeline summary and go to Run pipeline you should be able to go to Variables and change EnvironmentTag value.
Check your tag
Once your build is completed you can go to your build and check if you have your tag in there.
Use tags in release pipelines
Once we have our build tagged, we can use that information on the release pipeline level, and for example trigger, automatic trigger based on branch and tag. Go to your release pipeline and edit the Pre-deployment conditions for your stage. In this example, I want to do an automatic release of Prod stage once the build from branch main and with tag prod is created.
Often I have to make sure how I am visible to the world – what is my IP address that some service will see. I’ve found a great tool for that – ifconfig.me. You can see a lot of useful details via a browser but you can use it in console as well!
OK, so I had a problem with trying to figure out which variables are available for me and what are their values – Microsoft documentation is not always that helpful on that. As inspired by Mohit Goyal post I would like to share the same idea – on how to debug all the available variables but this time on those machines where you don’t have bash but powershell instead.
Just add to your pipeline PowerShell task, switch to inline script and fill the script
Get-ChildItem -Path Env:\ | Format-List
so it looks like
and after creation of a new release pipeline and execution of this pipeline you should have something like this: