Skip to main content

Using pvot in the Portal

pvot lives in the Infrastream Cloud Portal as a chat surface. You describe what you want; pvot proposes changes as pull requests or returns an analysis. This page covers the common workflows.

Authoring manifests​

Ask for the resource you need in plain language and let pvot produce the configuration:

"Create a private Cloud Storage bucket transaction-receipts in the payment-gateway project and give payment-api write access under the processed/ prefix."

pvot drafts the Bucket manifest and the application's accessControl block — starting from the platform's Samples & Templates so the output follows conventions — then opens a pull request for review. You review the diff exactly as you would a colleague's, and the Manifest Reference is one click away for any field.

Good prompts are specific about intent, not syntax:

  • "Add a BEFORE migration job to billing-service that runs /migrate.sh."
  • "Expose reports-api on reports.fincorp.com behind IAP for the fincorp-employees group."
  • "Scale the checkout DeploymentConfig to min 3 / max 20 in production only."

Troubleshooting and diagnosis​

pvot can read the live state graph and correlate it with Google Cloud signals, so you can ask operational questions directly:

"Why is the AstraPay database stuck provisioning?"

pvot traces the engine's run events and the resource's recorded error/root-cause information, cross-references live logs and metrics, and reports the specific cause (for example, a missing IAM binding or an exhausted quota) — often with the manifest change that would fix it.

Other examples:

  • "What changed in the payments project in the last hour, and by which PR?"
  • "Which services will be affected if I resize the ledger database?" (blast-radius analysis)

Audits and planning​

Use pvot to reason across the whole estate:

  • Security / compliance audits — "List any buckets granting public access," or "Find VMs in staging not attached to a secure subnet."
  • Architecture planning — "Draft the manifests to bootstrap a new trading platform with a release track, an AlloyDB database, and two services." pvot returns a complete, ordered set of manifests you can refine and submit.

What to remember​

  • pvot proposes; humans approve. Every change is a pull request gated by CODEOWNERS and ReleaseTrack approvals.
  • pvot is grounded — it works from your real state, the manifest schema, and the samples, so its output is valid and idiomatic by construction.
  • When in doubt about a field pvot used, check the Manifest Reference; when you want to see a full, correct example, browse Samples & Templates.