Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tags Assigned to Existing Revisions are Removed when Deploying CloudRun with PipeCD #4954

Open
twryJP opened this issue Jun 6, 2024 · 0 comments
Labels
kind/bug Something isn't working

Comments

@twryJP
Copy link

twryJP commented Jun 6, 2024

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:

  1. Assign tags to the existing revision of the target CloudRun.
  2. Deploy a new revision of the target CloudRun using PipeCD.
  3. Observe that the previously assigned tags are removed from the existing revision.

Environment:

  • piped version: v0.47.2
  • control-plane version:
  • Others:
@twryJP twryJP added the kind/bug Something isn't working label Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant