ACR
Last updated
Was this helpful?
Last updated
Was this helpful?
Azure Container Registry (ACR) is a fully-managed, private container registry service provided by Microsoft Azure. It is designed to store and manage container images and artifacts used in containerized application development and deployment. ACR integrates seamlessly with Azure's ecosystem and other tools, making it a vital component of cloud-native development workflows.
Delivery Shield gets notified for every build run in a pipeline. To identify the image for every build, it connects to the ACR repo and pulls the newly built image.
Once the image is pulled, it runs security scans on it. The scanned results are available in the Vulnerability Management page, and Artifact section of the DBOM page.
Navigate to Setup > Integrations.
In the Artifact panel, click ACR.
You can use the toggle button provided below the integration tile to enable or disable it as needed.
The ACR integration page is displayed. Click +New Account.
In the popup that appears, enter the details for the following:
Account Name - The name of the user account.
Repository- The name of the approved artifact repository from which the images are deployed. Security issues are raised by SSD if you try to deploy images from a different repository.
Host Url - The host Url link.
Username - The username to access the account.
Password - The password to access the account.
Select the Teams and the corresponding Environments from the dropdown for which you want the integration to be available. The integration will be available for the selected teams and environment only.
You can select up to 5 teams for the integration to be displayed.
An example is given below for reference:
In the example above,
if Team 1, Team 2, and Team 3 are selected, only applications associated with these teams can access the integration. Any applications belonging to other teams, such as Team 4, will not have access to this account.
Even if the user who created this account is also an admin for Team 4, the integration account remains restricted and is not available for Team 4.
Access to the account is strictly limited to the specified Teams and Environments selected during account creation.
For Organization Admins:
When an Organization Admin creates an account without selecting specific Teams and Environments, the account will be universally applicable, granting access to all teams and all environments by default.
For Team Admins with Multiple Teams:
If a Team Admin who manages multiple teams creates an account without specifying particular Teams and Environments, the account will only be accessible to the teams for which the logged-in user holds admin privileges.
Click Test to check if the entered values are valid. If the given values are valid, a popup appears at the top as shown below indicating it.
Once validated, click Save. The ACR account gets integrated in the artifact stage.
You can edit the entered values by clicking the three dots provided at the end of each added account. Click Edit.
Enter the new values and click Update.
The new values get updated.
