azurerm_postgresql_flexible_server_configuration: should lock the replica server#29071
azurerm_postgresql_flexible_server_configuration: should lock the replica server#29071stephybun merged 2 commits intohashicorp:mainfrom
azurerm_postgresql_flexible_server_configuration: should lock the replica server#29071Conversation
| locks.ByName(id.ConfigurationName, postgresqlFlexibleServerConfigurationResourceName) | ||
| defer locks.UnlockByName(id.ConfigurationName, postgresqlFlexibleServerConfigurationResourceName) | ||
|
|
There was a problem hiding this comment.
These were added recently in #27355 and seem to have fixed an issue so I don't think we should be removing them
There was a problem hiding this comment.
This lock is meaningless here and does not actually resolve the issue it was intended to. The issue still exists and needs further investigation. and there is already a lock to the flexible server above: locks.ByName(id.FlexibleServerName, postgresqlFlexibleServerResourceName).
There was a problem hiding this comment.
Could you resolve the merge conflicts so this can be merged?
c17951c to
9416609
Compare
* CHANGELOG.md for v4.25.0 * Update CHANGELOG.md #29126 * Update CHANGELOG.md #28647 * Update CHANGELOG.md #29153 * Update CHANGELOG.md #29131 * Update CHANGELOG.md #29090 * Update CHANGELOG.md #29137 * Update for #28781 * Update for #29158 * Update for #29073 * Update for #28149 * Update for #28730 * Update for #29157 * Update for #29135 * Update for #29184 * Update for #29093 * Update for #29071 * Update for #28371 * Update for #28560 * Update CHANGELOG.md #29199 * Update CHANGELOG.md for #29206 * prep for release * Update CHANGELOG.md --------- Co-authored-by: sreallymatt <106555974+sreallymatt@users.noreply.github.com> Co-authored-by: stephybun <steph@hashicorp.com> Co-authored-by: jackofallops <11830746+jackofallops@users.noreply.github.com> Co-authored-by: jackofallops <ste@hashicorp.com>
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
Community Note
Description
A locker to the replica server is also required when add a virutal endpoint. there is a internal ticket about updating configuration and creating virtual endpoint in parallel which caused an issue:
In mean time, the locker to the configuraiton name is not required while we already had a locker on the server itself.
PR Checklist
For example: “
resource_name_here- description of change e.g. adding propertynew_property_name_here”Testing
Change Log
Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.
azurerm_postgresql_flexible_server_configuration- add locker to the replication server idThis is a (please select all that apply):
Related Issue(s)
Fixes #0000
Note
If this PR changes meaningfully during the course of review please update the title and description as required.