gcloud artifacts repositories update - update an Artifact Registry repository

gcloud artifacts repositories update(REPOSITORY :--location=LOCATION)[--description=DESCRIPTION][--disable-remote-validation][--immutable-tags][--remote-password-secret-version=REMOTE_PASSWORD_SECRET_VERSION][--remote-username=REMOTE_USERNAME][--update-labels=[KEY=VALUE,…]][--upstream-policy-file=FILE][--allow-vulnerability-scanning    |--disable-vulnerability-scanning][--clear-labels    |--remove-labels=[KEY,…]][GCLOUD_WIDE_FLAG …]

This command can fail for the following reasons:

• A repository with this name does not exist.
• The active account does not have permission to update repositories.

Repository resource - The Artifact Registry repository to update. The argumentsin this group can be used to specify the attributes of this resource. (NOTE)Some attributes are not given arguments in this group but can be set in otherways.

To set theproject attribute:

• provide the argumentrepository on the command line with a fullyspecified name;
• provide the argument--project on the command line;
• set the propertycore/project.

This must be specified.

REPOSITORY

ID of the repository or fully qualified identifier for the repository.

To set therepository attribute:

• provide the argumentrepository on the command line.

This positional argument must be specified if any of the other arguments in thisgroup are specified.

--location=LOCATION

Location of the repository. Overrides the default artifacts/location propertyvalue for this command invocation. To configure the default location, use thecommand: gcloud config set artifacts/location.To set thelocation attribute:

• provide the argumentrepository on the command line with a fullyspecified name;
• provide the argument--location on the command line;
• set the propertyartifacts/location.

--description=DESCRIPTION

Description for the repository.

--disable-remote-validation

Do not make an HTTP request to validate the remote upstream. Not recommendedwhen setting a custom remote upstream unless you are absolutely sure yourupstream URI and any auth is valid.

--immutable-tags

(Docker only) Prevent changes to tagged images in the repository. Tags cannot bedeleted or moved to a different image digest, and tagged images cannot bedeleted.

--remote-password-secret-version=REMOTE_PASSWORD_SECRET_VERSION

Secret Manager secret version that contains password for the remote repositoryupstream.

--remote-username=REMOTE_USERNAME

Remote Repository upstream registry username.

--update-labels=[KEY=VALUE,…]

List of label KEY=VALUE pairs to update. If a label exists, its value ismodified. Otherwise, a new label is created.

Keys must start with a lowercase character and contain only hyphens(-), underscores (_), lowercase characters, andnumbers. Values must contain only hyphens (-), underscores(_), lowercase characters, and numbers.

--upstream-policy-file=FILE

(Virtual Repositories only) is the upstreams for the Virtual Repository. Exampleof the file contents: [ { "id": "test1", "repository":"projects/p1/locations/us-central1/repositories/repo1", "priority": 1 }, { "id":"test2", "repository": "projects/p2/locations/us-west2/repositories/repo2","priority": 2 } ]

At most one of these can be specified:

--allow-vulnerability-scanning

Allow vulnerability scanning on the repository.

--disable-vulnerability-scanning

Disable vulnerability scanning on the repository.

At most one of these can be specified:

--clear-labels

Remove all labels. If--update-labels is also specified then--clear-labels is applied first.

For example, to remove all labels:

gcloudartifactsrepositoriesupdate--clear-labels

To remove all existing labels and create two new labels,foo andbaz:

gcloudartifactsrepositoriesupdate--clear-labels--update-labelsfoo=bar,baz=qux

--remove-labels=[KEY,…]

List of label keys to remove. If a label does not exist it is silently ignored.If--update-labels is also specified then--update-labels is applied first.

Run$gcloud help for details.