This article explains how to manage image registries in SWIFT after adding your any registry. You can rediscover to refresh available repositories, configure to update authentication or settings, and delete to remove the registry from SWIFT
Pre-requisite:
1. Image registry should be added in SWIFT.
Topics covered:
Rediscover
1. To rediscover an existing image registry, go to Container Registries and select the image registry you want to rediscover. Rediscover means refreshing or re-scanning the connected image registry to fetch the latest list of repositories and images.
2. When you click on registry, you can check images and repositories. You can identify the images. Click on added image registry .
3. You will be able to see all the images and repositories present in the image registry. Any newly created images will also be displayed here. Please refer to the screenshot below – simply navigate to the Image Repositories tab to view them.
Configure
Use cases:
1. The registry credentials (username/password, token) have changed and need to be updated to maintain connectivity.
2. The registry endpoint or URL has changed (for example, you moved to a different container registry or a new project/namespace).
3. You want to switch to a different container registry (e.g., from a public registry to a private one, or from one cloud provider to another).
1. To configure an existing image registry, go to Container Registries and select the image registry you want to configure.
2. Once you click Configure, a new pop-up window will open where you can update the connection details for the registry, such as authentication credentials and email. Please refer to the screenshot below.
Similarly for the other clouds you can change the parameters with the configure option in SWIFT.
#For Docker configuration, you can configure below fields.
| Field | Field Description |
| Password | You can change the password. If you want to update any new password for docker registry. |
| User Email | If you want to change the email, then you can change in configure option of that docker registry. |
#For OCIR Configuration, you can update/change the configuration.
| Field | Field Description |
| User ID | The unique identifier of your Oracle Cloud user account. |
| Compartment ID | The OCID of the compartment where your registry resources are located. |
| API key fingerprint | The fingerprint of the API key you uploaded to Oracle Cloud, used for secure authentication. |
| Username | Used as part of login credentials when authenticating to OCIR from SWIFT |
| Tenancy Namespace | he unique namespace assigned to your tenancy, used to access your OCIR. |
| Auth Token | If you want to update or change the token, then you can do it. |
| Private Key File | For security compliance, if you need to create a new API key and update it in the existing OCIR configuration, you can do it this way: |
| User Email | If you want to add a different team member to receive notifications related to the registry, you can update the User Email field in SWIFT accordingly. |
#For ACR Configuration, you can update/change the configuration
| Field | Field Description |
| Client ID | When you need to update the Client ID for an existing ACR configuration, you can do it using this option in SWIFT. |
| Registry Password | For security best practices, such as regularly rotating passwords or when a password expires, you need to update the registry password. You can use this option in SWIFT to change the password for the existing registry configuration. |
| Client Secret | For security best practices, such as regularly rotating the client secret or when the secret expires, you need to update the client secret. You can use this option in SWIFT to update the client secret for the existing ACR configuration |
| User email | For notification management, if you need to change the user email (for example, when adding a new team member or replacing an existing one), you can use this option in SWIFT to update the email address for the existing registry configuration. |
#For GAR configuration
| Field | Field Description |
| Private key file | For security best practices, such as rotating service account keys or when the existing private key file is compromised or invalid, you need to update the private key file. You can use this option in SWIFT to upload the new private key file for the existing GAR configuration. |
Delete
1. To delete an existing image registry, go to Container Registries and select the image registry you want to delete.
2. Once clicked on Delete button, then Image registry will be removed from SWIFT. We can delete the Image registry when it no longer in use. If you want to clean up unused or outdated registry connections.
3. It will start to delete the image registry.
4. Nothing will be showing there after deletion.
