-
Notifications
You must be signed in to change notification settings - Fork 206
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
IAMPolicyMember GoClient resourceRef type doesn't match schema in document #413
Comments
Hi @micnncim , thank you for reporting the issue. We'll look into fixing it. Will post updates when we have new information. |
@maqiuyujoyce Hi, how is the progress? Anything I can help with? |
Hi @micnncim thank you for your follow up and offering for help! We are still working on it. Will post updates when the fix is out. |
Gently pinging this thread to mention that this issue is blocking us from sunsetting our homerolled KCC Go types. |
Hi @aw185176, thanks for elaborating on the impact that this issue has on you. Such details help us with prioritization. A fix is currently being worked on, and the estimate of a "few weeks" given in the other thread still holds true. We'll update this thread when the fix is released. |
The issue should be fixed in Config Connector v1.50.0. |
Checklist
Bug Description
I'm trying to use the Go client package for
IAMPolicyMember
based on https://cloud.google.com/config-connector/docs/reference/resource-docs/iam/iampolicymember#external_project_level_policy_member. But the package doesn't match the schema in the document.In the doc:
In the package (https://github.com/GoogleCloudPlatform/k8s-config-connector/blob/f158208856e727336001b17397cbaa4c918d2ba4/pkg/apis/k8s/v1alpha1/condition_types.go#L29-L37):
Therefore, I can't specify a response properly.
Additional Diagnostic Information
Kubernetes Cluster Version
N/A
Config Connector Version
N/A
Config Connector Mode
N/A
Log Output
N/A
Steps to Reproduce
Steps to reproduce the issue
$ go get github.com/GoogleCloudPlatform/k8s-config-connector@1.40.0
YAML snippets
N/A
The text was updated successfully, but these errors were encountered: