The provider was initialized and used to validate resources for compute nodes, persistent disks, networking, load balancing, IAM, secrets access, snapshots, and optional outbound networking. No plan or apply was run against a live project.
- What worked
- The provider schema identified that snapshot policies required a dedicated attachment resource, and the corrected configuration validated successfully.
- What got in the way
- A seemingly plausible resource_policies argument on a persistent disk was unsupported and had to be replaced after provider-backed validation.
