feat: [container] add etags for cluster and node pool update operations #8930
Conversation
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
Clients may now optionally specify the previously read etag for a cluster or node pool during update requests. The etag is regenerated every time the object is updated. If an etag is provided, it will be checked against the current etag, and the request will be rejected on mismatch. This is particularly useful for allowing two clients to concurrently update a repeated field without overwriting each other. PiperOrigin-RevId: 498249600 Source-Link: googleapis/googleapis@9a294bf Source-Link: https://github.com/googleapis/googleapis-gen/commit/f0f0e1ffc3e28e203e7c233af4936688c9b2b07f Copy-Tag: eyJwIjoiamF2YS1jb250YWluZXIvLk93bEJvdC55YW1sIiwiaCI6ImYwZjBlMWZmYzNlMjhlMjAzZTdjMjMzYWY0OTM2Njg4YzliMmIwN2YifQ==
zhumin8
approved these changes
Dec 29, 2022
Merged
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.
Clients may now optionally specify the previously read etag for a cluster or node pool during update requests. The etag is regenerated every time the object is updated. If an etag is provided, it will be checked against the current etag, and the request will be rejected on mismatch. This is particularly useful for allowing two clients to concurrently update a repeated field without overwriting each other.
PiperOrigin-RevId: 498249600
Source-Link: googleapis/googleapis@9a294bf
Source-Link: https://github.com/googleapis/googleapis-gen/commit/f0f0e1ffc3e28e203e7c233af4936688c9b2b07f
Copy-Tag: eyJwIjoiamF2YS1jb250YWluZXIvLk93bEJvdC55YW1sIiwiaCI6ImYwZjBlMWZmYzNlMjhlMjAzZTdjMjMzYWY0OTM2Njg4YzliMmIwN2YifQ==