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

google_sql_user not able to create for myssql #12049

Closed
hanumantharao19 opened this issue Jul 7, 2022 · 5 comments
Closed

google_sql_user not able to create for myssql #12049

hanumantharao19 opened this issue Jul 7, 2022 · 5 comments
Assignees
Labels

Comments

@hanumantharao19
Copy link

module.mssql.google_sql_user.additional_users["qa"]: Still creating... [10s elapsed]

│ Error: Error setting disabled: Invalid address to set: []string{"disabled"}

│ with module.mssql.google_sql_user.additional_users["prod"],
│ on ../modules/mssql/main.tf line 167, in resource "google_sql_user" "additional_users":
│ 167: resource "google_sql_user" "additional_users" {



│ Error: Error setting disabled: Invalid address to set: []string{"disabled"}

│ with module.mssql.google_sql_user.additional_users["dev"],
│ on ../modules/mssql/main.tf line 167, in resource "google_sql_user" "additional_users":
│ 167: resource "google_sql_user" "additional_users" {



│ Error: Error setting disabled: Invalid address to set: []string{"disabled"}

│ with module.mssql.google_sql_user.additional_users["qa"],
│ on ../modules/mssql/main.tf line 167, in resource "google_sql_user" "additional_users":
│ 167: resource "google_sql_user" "additional_users" {

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
  • Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.
  • If an issue is assigned to the 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 to hashibot, a community member has claimed the issue already.

Terraform Version

Affected Resource(s)

  • google_XXXXX

Terraform Configuration Files

# Copy-paste your Terraform configurations here.
#
# For large Terraform configs, please use a service like Dropbox and share a link to the ZIP file.
# For security, you can also encrypt the files using our GPG public key:
#    https://www.hashicorp.com/security
#
# If reproducing the bug involves modifying the config file (e.g., apply a config,
# change a value, apply the config again, see the bug), then please include both:
# * the version of the config before the change, and
# * the version of the config after the change.

Debug Output

Panic Output

Expected Behavior

Actual Behavior

Steps to Reproduce

  1. terraform apply

Important Factoids

References

  • #0000
@edwardmedia edwardmedia self-assigned this Jul 7, 2022
@edwardmedia
Copy link
Contributor

edwardmedia commented Jul 7, 2022

@hanumantharao19 can you share your config and the full debug log? Does the example work for you?

@srs2210
Copy link

srs2210 commented Jul 15, 2022

I was able to replicate this issue as well and this error occurs when deploying the google_sql_user resource.

Code:

resource "google_sql_user" "default" {
  name       = "default"
  project    = "test-project"
  instance   = "sqlusertest"
  password   = "***********"
}

Output/Error:

│ Error: Error setting disabled: Invalid address to set: []string{"disabled"}
│ 
│   with google_sql_user.default,
│   on main.tf line 11, in resource "google_sql_user" "default":
│   11: resource "google_sql_user" "default" {

I believe the issue originates from the PR# 11834 where modifications were made to google_sql_user resource in provider version v4.25.0. Because using google provider >= 4.25.0 throws this error (I have tested this).

Using google provider version 4.24.0 resolves the issue so this is a temporary workaround.

P.S. - The issue mentions mysql, whereas I was creating a user for SQL Server. So I think it is an issue for all types of SQL instances.

@edwardmedia
Copy link
Contributor

#11891

@edwardmedia
Copy link
Contributor

closing this as a dup #11891

@github-actions
Copy link

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants