Tags Assigned to Existing Revisions are Removed when Deploying CloudRun with PipeCD
@niladrix719 is already working on this.
Since May 19, 2025.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 364
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 84
Description
What happened:
When deploying a new revision of CloudRun with PipeCD, tags assigned to existing revisions are removed. Specifically, when tags are allocated to an existing revision of CloudRun and a new deployment is carried out via PipeCD, the tags that were previously assigned to the existing revision are removed.
I added the following code to the spec.pipeline.stages in app.pipecd.yaml and redeployed. As a result, the traffic to the revision deployed by PipeCD was 0%, but similar to the previous case, the tags assigned before the deployment were removed from the existing revision.
pipeline:
stages:
- name: CLOUDRUN_PROMOTE
with:
percent: 0
What you expected to happen:
Deploying CloudRun with PipeCD should not affect the tags assigned to existing revisions.
How to reproduce it:
- Assign tags to the existing revision of the target CloudRun.
- Deploy a new revision of the target CloudRun using PipeCD.
- Observe that the previously assigned tags are removed from the existing revision.
Environment:
pipedversion: v0.47.2control-planeversion:- Others:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.