summaryrefslogtreecommitdiff
path: root/contrib/imgts
diff options
context:
space:
mode:
authorChris Evich <cevich@redhat.com>2019-06-05 15:52:56 -0400
committerChris Evich <cevich@redhat.com>2019-06-05 15:53:00 -0400
commit32fb83e3ab7fd9f61143601a015dc8fa8af09de1 (patch)
tree7a2f19483e6e8ed854ab151dbe4183618a842b11 /contrib/imgts
parentb1c9cb712db0e5cdc9f3b5f188c5c0083ab00fc6 (diff)
downloadpodman-32fb83e3ab7fd9f61143601a015dc8fa8af09de1.tar.gz
podman-32fb83e3ab7fd9f61143601a015dc8fa8af09de1.tar.bz2
podman-32fb83e3ab7fd9f61143601a015dc8fa8af09de1.zip
Cirrus: Track VM Image calling GCE project
With multiple `containers` projects updating VM Image metadata, it would be very difficult to discover which Cirrus-CI setup was responsible. Add the GCE project name to the list of metadata labels to update when this container runs. This will give more context as to which images are currently in use. Signed-off-by: Chris Evich <cevich@redhat.com>
Diffstat (limited to 'contrib/imgts')
-rwxr-xr-xcontrib/imgts/entrypoint.sh1
1 files changed, 1 insertions, 0 deletions
diff --git a/contrib/imgts/entrypoint.sh b/contrib/imgts/entrypoint.sh
index 65a76d8e4..610e1f3b6 100755
--- a/contrib/imgts/entrypoint.sh
+++ b/contrib/imgts/entrypoint.sh
@@ -32,6 +32,7 @@ ARGS="--update-labels=last-used=$(date +%s)"
# optional
[[ -z "$BUILDID" ]] || ARGS="$ARGS --update-labels=build-id=$BUILDID"
[[ -z "$REPOREF" ]] || ARGS="$ARGS --update-labels=repo-ref=$REPOREF"
+[[ -z "$GCPPROJECT" ]] || ARGS="$ARGS --update-labels=project=$GCPPROJECT"
gcloud config set account "$GCPNAME"
gcloud config set project "$GCPPROJECT"