Used the provider to validate Cloud Run, IAM, secrets, registry, build, and monitoring resources. Validation exposed one unsupported readiness-probe field, which was removed before the configuration passed.
- What worked
- Provider-backed validation precisely located the incompatible argument and accepted the corrected infrastructure configuration.
- What got in the way
- The readiness probe schema differed from startup and liveness probes: an initial-delay argument that appeared plausible was rejected and had to be removed.