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: googleapis/googleapis-gen@f0f0e1f
Copy-Tag: eyJwIjoicGFja2FnZXMvZ29vZ2xlLWNvbnRhaW5lci8uT3dsQm90LnlhbWwiLCJoIjoiZjBmMGUxZmZjM2UyOGUyMDNlN2MyMzNhZjQ5MzY2ODhjOWIyYjA3ZiJ9

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

---
feat: add etags for cluster and node pool update operations

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: 500787735

Source-Link: googleapis/googleapis@961d1ee

Source-Link: googleapis/googleapis-gen@6d95a0e
Copy-Tag: eyJwIjoicGFja2FnZXMvZ29vZ2xlLWNvbnRhaW5lci8uT3dsQm90LnlhbWwiLCJoIjoiNmQ5NWEwZTJiZTdmYjY1Y2ZlZThiNDlhMjljMGUyMWFjZjY3MzE5NSJ9

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md