To give FeaturePeek the credentials to pull images from Azure Container Registry, you need to ensure that a few environment variables are present in your CI environment.
You can use any CI provider to push to ACR, although it's most likely that you're using Azure Pipelines. To learn more about defining variables for Azure Pipelines, read how to set variables in your pipeline.
Note: This chapter is only applicable if you push images to Azure Container Registry.
You'll need to pass in the
-p flag when pinging FeaturePeek in your CI pipeline.
Be sure to call this after your build step.
Required environment variables
There are three environment variables that are required to be set:
ACR_REGISTRY_IDmust always be set.
- If you authenticate to ACR via username/password,
ACR_PASSWORDmust be set.
- If you authenticate to ACR via service principal,
ACR_SP_PASSWDmust be set.
Your registry identifier that appears as the subdomain of azurecr.io.
Your ACR username. If this environment variable is present,
ACR_PASSWORD must also be present.
Your ACR password. If this environment variable is present,
ACR_USER_NAME must also be present.
The UUID of your service principal. If this environment variable is present,
ACR_SP_PASSWD must also be present.
Your service principal password. If this environment variable is present,
ACR_SP_ID must also be present.
Example pipeline file
While you can use any Continuous Integration provider to push to Azure Container Registry, here's an example configuration file using Azure Pipelines.