Google Cloud setup waits for new access grants
Google Cloud connection setup (Beta) now retries access bindings when a newly created service account is not immediately available. The retries are bounded, and setup still stops if access cannot be granted. You can rerun the same command after a failed setup; it reuses the resources already created.
CPU verification workloads now use the host maintenance policy required by Google Cloud’s general-purpose machines. GPU workloads retain their required stop-on-maintenance policy.
Cloud and pool CLI commands preserve the API’s explanation, recovery command and request ID when a request fails. An unfinished cloud connection now tells you how to resume setup instead of reporting a generic conflict.
Azure spend reports identify Azure Cost Management as their source and include Virtual Machines charges in the compute subtotal. Google billing reports describe the selected-project scope used by their export query.
Host enrollment downloads the exact agent release named by its installer, so a deployment between fetching the command and running it does not cause a checksum mismatch.