You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
inapp.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.What you expected to happen:
Deploying CloudRun with PipeCD should not affect the tags assigned to existing revisions.
How to reproduce it:
Environment:
piped
version: v0.47.2control-plane
version:The text was updated successfully, but these errors were encountered: