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

[Bug]: Import of tag resources failed with 403 error #627

Open
1 task done
nlevee opened this issue Sep 27, 2024 · 2 comments
Open
1 task done

[Bug]: Import of tag resources failed with 403 error #627

nlevee opened this issue Sep 27, 2024 · 2 comments
Labels
bug Something isn't working needs:triage

Comments

@nlevee
Copy link

nlevee commented Sep 27, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Affected Resource(s)

tags.gcp.upbound.io/v1beta1 - TagBinding
tags.gcp.upbound.io/v1beta1 - TagKey
tags.gcp.upbound.io/v1beta1 - TagValue

Resource MRs required to reproduce the bug

apiVersion: tags.gcp.upbound.io/v1beta1
kind: TagKey
metadata:
  annotations:
    meta.upbound.io/example-id: tags/v1beta1/tagkey
    upjet.upbound.io/manual-intervention: "The resource requires a real external name"
    crossplane.io/external-name: "tagKeys/281475435132414"
  labels:
    testing.upbound.io/example-name: key-external
  name: key-external
spec:
  managementPolicies: ["Observe"]
  forProvider: {}

Steps to Reproduce

Create a resource TagKey, TagValue or TagBinding with label crossplane.io/external-name and managementPolicies = ["Observable"]

What happened?

Currently, the import fails with at best a 403 error:

image

Relevant Error Output Snippet

No response

Crossplane Version

1.17.0

Provider Version

1.8.1

Kubernetes Version

No response

Kubernetes Distribution

GKE

Additional Info

No response

Copy link

This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

@github-actions github-actions bot added the stale label Dec 27, 2024
@nlevee
Copy link
Author

nlevee commented Dec 28, 2024

/fresh PR is still open

@github-actions github-actions bot removed the stale label Dec 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs:triage
Projects
None yet
Development

No branches or pull requests

1 participant