[from bielski:]
The image tagging in cloud-build/02-dev-to-staging-auto-promo script fails.
Why does it fail?
In order to recreate an existing tag (which the used gcloud command seems to do), the service account would need artifactregistry.tags.delete permission which is not included in the artifactregistry.writer role.
There are multiple tags that are potentially being overwritten:
latest
latest-cb2
$DOCKER_IMAGE_VERSION is the same as vSUPERDUPER_MAGIC_VERSION which also creates a conflict.
Solutions:
a) give an additional role to cloud build svc acc (roles/artifactregistry.repoAdmin)
b) prevent tagging duplicates (which would prevent us from using latest tag)
[from bielski:]
The image tagging in cloud-build/02-dev-to-staging-auto-promo script fails.
Why does it fail?
In order to recreate an existing tag (which the used gcloud command seems to do), the service account would need artifactregistry.tags.delete permission which is not included in the artifactregistry.writer role.
There are multiple tags that are potentially being overwritten:
latest
latest-cb2
$DOCKER_IMAGE_VERSION is the same as vSUPERDUPER_MAGIC_VERSION which also creates a conflict.
Solutions:
a) give an additional role to cloud build svc acc (roles/artifactregistry.repoAdmin)
b) prevent tagging duplicates (which would prevent us from using latest tag)