LocalCloud jobs should fail closed on missing health or env vars.
Glossary
Agentic CI
A CI workflow where an AI agent helps create or maintain validation steps, while the actual job remains deterministic, reviewable, and bounded.
Do not mix local emulator checks with deployment secrets.
What Agentic CI means here
A CI workflow where an AI agent helps create or maintain validation steps, while the actual job remains deterministic, reviewable, and bounded.
- LocalCloud jobs should fail closed on missing health or env vars.
- Do not mix local emulator checks with deployment secrets.
How to use the term safely
In LocalCloud content, this term should not imply production replacement, legal permission, hidden credentials, or complete cloud parity. It describes a bounded local-development workflow that still needs license review and release validation against real Google Cloud.
Use the sandbox deliberately
- Permitted workflows use local endpoint values and should stop rather than fall back to real Google Cloud or real credentials. The Public Preview License permits individuals and organizations, including for-profit companies, to use LocalCloud for non-production internal development, testing, CI, evaluation, and pilots.
- LocalCloud emulates bounded local development workflows. Validate application behavior against real Google Cloud before production deployment.
- Before production deployment, unset LocalCloud emulator environment variables and validate behavior against real Google Cloud.
Keep the agent on the supported path
- Agent routes — Agent sandbox entry points.
- Compatibility — Service support boundaries.
- Compatibility matrix — Check current support boundaries before relying on a local-only test.
- Service catalog — Review every LocalCloud service, endpoint, and limitation.
- SDK examples — Use standard Google Cloud SDKs pointed at localhost.
- Seed data — Load deterministic fixtures for repeatable agent and CI runs.