-
Notifications
You must be signed in to change notification settings - Fork 55
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
gcp:sql/user:User Error setting disabled: Invalid address to set: []string{"disabled"} #861
Comments
Moving to pulumi-gpc, this looks like an error in the provider read method. |
Here are my thoughts upon further investigation. I have tried to manually call the GCP rest API to list all users. This is how the response looks like:
My guess is that the issues comes from the Upon further checks, it seems this was typed properly in |
Marking this a duplicate of #850 |
As mentioned in #850, this is unfortunately coming from the underlying terraform provider. The terraform bug is tracked there. Thanks for trying to fix this in #863 but sadly that will not fix it since the pulumi gcp provider automatically generates against the spec from the underlying terraform provider. |
I believe this is what we're waiting on being fixed - hashicorp/terraform-provider-google#11891 |
What happened?
I have started getting an error on refresh, related to a gcp sql User. The error states this:
I have tried to remove the user from the stack manually and import it again, but getting the same error on import.
I can't understand what is this error related to, since there is no such property 'disabled' on the user level.
Steps to reproduce
Expected Behavior
Should work or at least show a meaningful error
Actual Behavior
Refresh/import fails. Up is ok for other resources of the stack
Versions used
Additional context
Here is the user object:
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: