-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
azurerm_postgresql_server
fix acctests and issues ssl_enforcement_enabled
cannot be updated
#7558
Conversation
azurerm_postgresql_server
fix issues ssl_enforcement_enabled
cannot be updatedazurerm_postgresql_server
fix acctests and issues ssl_enforcement_enabled
cannot be updated
@tombuildsstuff Thanks for comments. I have merged the changes and correspond to #6809, to deprecate the deprecated fields. Tests have been passed. |
Hey, as this is a breaking change that should wait till 3.0 i am going to close this and we can then reopen it for 3.0. |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
fix #7397
#7475
#8084
#8314
Except issues, several minor issues in acctest have been fixed:
infrastructure_encryption_enabled
andgeo_redundant_backup
cannot be updated, updating these fields has been removed.hasChange
judgement for all deprecated fields in update, avoiding they'll not be updated too.storage_mb
could not be updated to downscale,create_replica
andcreate_PITR
has the same sku with the source db, etc.tests: