Skip to main content

Use Beck

Beck is a chat in the Infrastream portal. You describe what you want. Beck opens a pull request or returns an analysis. Be specific about the intent. You do not need to know the syntax.

Write manifests​

Ask for the resource. Beck starts from the samples, writes the manifests and opens a pull request. Review the diff as you would review a colleague's work.

  • "Create a private Cloud Storage bucket transaction-receipts in the payment-gateway project. Give payment-api write access under processed/."
  • "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 and max 20 in production only."
  • "What is the schema for a Database manifest?"
  • "Lint these proposed YAML files against our repository before we open a pull request."

Diagnose​

Beck reads the live state graph and Google Cloud signals. It reports the cause, and often the manifest change that fixes it.

  • "Why is the AstraPay database stuck provisioning?"
  • "What changed in the payments project in the last hour, and in which pull request?"
  • "Which services does a resize of the ledger database affect?"

Audit and plan​

  • "List any buckets that grant public access."
  • "Draft the manifests for a trading platform with a release track, an AlloyDB database and two services."
  • "List the recent deployments that wait for approval."
  • "Show the stage history and error log of the latest release."
  • "Show the dependency graph that connects our environments and services."

For broad design or code work, ask Beck to hand the task to a squad. The Planning Squad designs and plans migrations. The Engineering Squad writes, tests and debugs code.

Remember​

  • Beck proposes. You merge. Your branch rules decide how strictly the team reviews a change.
  • Check a field that Beck used in the Manifest Reference.

Next​