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
resource/aws_dms_endpoint: send postgres_settings on Modify
Fixes a bug where ModifyEndpoint did not include `PostgreSQLSettings`
when only the nested `postgres_settings` block changed (e.g. toggling
`heartbeat_enable` or setting `heartbeat_schema`). Previously the
Update logic only attached `PostgreSQLSettings` when top-level
connection or secrets fields changed, so nested-only diffs were lost.
Implementation:
* Build a single `PostgreSQLSettings` object for the update.
* If `postgres_settings` changed, expand and attach those fields.
* If top-level connection or secrets fields changed, overlay those
onto the same object and, for the non-secrets path, call
`expandTopLevelConnectionInfoModify` to keep top-level fields in sync.
* Ensure `EngineName` is set so DMS accepts the modify call.
Tests:
* Add `TestAccDMSEndpoint_PostgreSQL_settings_update` to toggle
`heartbeat_enable` and set `heartbeat_schema`, verifying that
nested-only changes are applied.
No schema changes, no docs changes.
Fixes#35834
0 commit comments