Add support for log_stream_override on replicas#84
Merged
tuckerchapin merged 3 commits intoMay 12, 2026
Conversation
…set -> list, regens docs, and fixes old missing docs update for pg18 support
tuckerchapin
requested review from
jakemalachowski,
kitemongerer,
mdbenjam and
wendorf
as code owners
tuckerchapin
commented
May 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Already supported elsewhere, but not exposed in our terraform provider yet. This adds support for log stream overrides on replicas.
The biggest change here is switching
read_replicasfromSettoList. It appears that a Set breaks at apply with "inconsistent values for sensitive attribute" when the Computed value transitions unknown→"". The alternatives to this seemed overly cumbersome: replica-specific schemas, making the override in a parallel list and trying to map. This change is still a noop and should only surface as a positional diff if a user reorders their replicas (why?).Also random little docs fix.