-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
google_sql_user
: Error setting disabled: Invalid address to set since 4.25.0
#11891
Comments
Also experiencing this issue today and pinning to 4.24.0 to avoid and agree this is a regression. |
Very strange, it looks like during the Read function we set an invalid value that isn't in the schema, but I would expect this to fail during the test. It appears we aren't receiving this block back from the API which is why the test hasn't been failing. @lra are you able to provide a debug log that shows the GET request that is issued and the corresponding response that I suspect has the sql_server_user_details block set to I can confirm this? |
There you go, I had to redact a few things, I also used the latest versions:
|
b/239809673 |
Is there any work around to this issue apart from using an old provider version? I can't use an old provider due to needing fixes in the newer provider for other provider issues. |
Why is this labeled as upstream? This seems to be a provider issue. |
I think there's some confusion around how this field should work. The API apparently doesn't support setting it: GoogleCloudPlatform/magic-modules#6165 (review) But in some cases it seems to? |
does this mean it's impossible to create a MS SQL user via Terraform currently? |
Closed by GoogleCloudPlatform/magic-modules#6165 |
Will there be a release with this fixed? Just re-tested with the most recent release and it's still broken. Thanks. |
From what I can tell, this will likely be out in the |
works with 4.41 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
modular-magician
user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned tohashibot
, a community member has claimed the issue already.Terraform Version
Affected Resource(s)
Terraform Configuration Files
We are using the official
terraform-google-sql-db
module: https://github.com/terraform-google-modules/terraform-google-sql-db/blob/master/modules/mssql/main.tf#L174-L180Debug Output
Expected Behavior
Actual Behavior
Steps to Reproduce
source = "GoogleCloudPlatform/sql-db/google//modules/mssql"
and thehashicorp/google
set to 4.240.hashicorp/google
to 4.25.0References
I think the bug has been introduced by #11834
The text was updated successfully, but these errors were encountered: