-
Notifications
You must be signed in to change notification settings - Fork 1.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
Add support for cross bucket replication feature #12562
Merged
NickElliot
merged 3 commits into
GoogleCloudPlatform:main
from
googlyrahman:replication
Dec 26, 2024
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the need of DiffSuppressFunc?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question! I'll give some context:
When using cross bucket replication feature, i.e specifying
replication_spec
, the backend would setupevent_stream
on it's own, and it can't be configurable via user, Hence showingcomputed
behvior, However we can't mark itcomputed
as the field is configurable while usingtransfer_spec
.So first time when you do
terraform apply
, theevent_stream
would be stored in file, and in nextterraform plan
it would show a diffSOMETHING -> ""
One alternative to this is to not store
eventStream
at all inRead
while usingreplication
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From the context, Can we use Optional+Computed and ConflictsWith(event_stream and replication_spec)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Keeping it
Optional+Computed
would showevent_stream (known after apply)
despite not specifyingevent_stream
while working withtransfer_spec
.But i think, it should be fine - I've updated code to reflect the same!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also please consider a case when user removes
event_stream
from the config expect it to be removed from the resource. If the attribute is computed then terraform won't consider this change as necessary and won't show any diff. If that is expected then this solution should work otherwise we need to verify if empty list can be used as not-present indicator or not.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on the offline conversation, we're moving forward with
diffSupressFunc
as written earlier.