You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
We should be able to start/stop cloud sql instances using activation_policy
Actual Behavior
activation_policy="NEVER" brings the instance down. But activation_policy="ALWAYS" does not bring the instance up.
Steps to Reproduce
Create an instance with activation_policy="ALWAYS"
Change activation_policy="NEVER" and do "terraform apply" (This will bring the instance down)
Change activation_policy="ALWAYS" and do "terraform apply". This will throw the error
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
~ update in-place
Terraform will perform the following actions:
# google_sql_database_instance.cloudsql will be updated in-place
~ resource "google_sql_database_instance" "cloudsql" {
id = "testdb"
name = "testdb"
# (13 unchanged attributes hidden)
~ settings {
~ activation_policy = "NEVER" -> "ALWAYS"
# (11 unchanged attributes hidden)
# (4 unchanged blocks hidden)
}
}
Plan: 0 to add, 1 to change, 0 to destroy.
Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.
Enter a value: yes
google_sql_database_instance.cloudsql: Modifying... [id=testdb]
╷
│ Error: Error, failed to patch instance settings for : googleapi: Error 400: Invalid request: Instance properties other than activation policy are not allowed to be updated when the instance is stopped and not started in the same operation.., invalid
│
│ with google_sql_database_instance.cloudsql,
│ on cloudsql.tf line 10, in resource "google_sql_database_instance" "cloudsql":
│ 10: resource "google_sql_database_instance" "cloudsql" {
│
╵
The text was updated successfully, but these errors were encountered:
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.
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
1.3.6
Affected Resource(s)
Terraform Configuration Files
Debug Output
https://gist.github.com/nvsajeeva/04941e3dca0875dfe1e9b1ed62fe0362
Panic Output
Expected Behavior
We should be able to start/stop cloud sql instances using activation_policy
Actual Behavior
activation_policy="NEVER" brings the instance down. But activation_policy="ALWAYS" does not bring the instance up.
Steps to Reproduce
The text was updated successfully, but these errors were encountered: