Skip to content
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

feat: [container] add etags for cluster and node pool update operations #8930

Merged
merged 2 commits into from
Dec 29, 2022

Conversation

gcf-owl-bot[bot]
Copy link
Contributor

@gcf-owl-bot gcf-owl-bot bot commented Dec 29, 2022

  • Regenerate this pull request now.

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==

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==
@trusted-contributions-gcf trusted-contributions-gcf bot added kokoro:force-run Add this label to force Kokoro to re-run the tests. owlbot:run Add this label to trigger the Owlbot post processor. labels Dec 29, 2022
@gcf-owl-bot gcf-owl-bot bot removed the owlbot:run Add this label to trigger the Owlbot post processor. label Dec 29, 2022
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Dec 29, 2022
@trusted-contributions-gcf trusted-contributions-gcf bot added kokoro:force-run Add this label to force Kokoro to re-run the tests. owlbot:run Add this label to trigger the Owlbot post processor. labels Dec 29, 2022
@gcf-owl-bot gcf-owl-bot bot removed the owlbot:run Add this label to trigger the Owlbot post processor. label Dec 29, 2022
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Dec 29, 2022
@zhumin8 zhumin8 added the automerge Merge the pull request once unit tests and other checks pass. label Dec 29, 2022
@gcf-merge-on-green gcf-merge-on-green bot merged commit bcd0111 into main Dec 29, 2022
@gcf-merge-on-green gcf-merge-on-green bot deleted the owl-bot-copy-java-container branch December 29, 2022 17:10
@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Dec 29, 2022
@release-please release-please bot mentioned this pull request Jan 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants