formae-import

Use when the user wants formae to manage a credential: generate a password, rotate a secret, wire a database password or key pair, reference a secret from…

Use when the user is deciding how to group resources into stacks, where to draw stack boundaries, or how stacks/targets/policies relate — stack design and…

Use when the user needs to make an urgent targeted infrastructure change, hotfix, incident response fix, or patch without a full reconcile

Use for cloud infrastructure inventory questions even without naming formae: which GCP storage buckets, AWS S3 buckets, Azure resources, deployed resources…

Use when the user wants to check infrastructure drift or explicitly absorb or revert out-of-band changes, with or without a maintained IaC codebase

Use when the user wants to deploy infrastructure, apply a forma file, reconcile a stack, update a stack, or make planned infrastructure changes

Use when the user wants to start authoring formae infrastructure or deploy something NEW with formae — e.g.

Use when the user wants to connect a cloud account to their hosted formae installation, or add another one — e.g.

Use when the user wants to add or remove a plugin schema dependency in an existing formae project's PklProject — e.g.

Use when the user wants to start a brand-new formae project from scratch (no existing IaC codebase) — scaffolds a project with `formae project init`, infers…

Use when the user wants to rename a managed resource, relabel a resource, change a resource's label, or give a discovery-named resource a readable name — a…

Use when the user wants to set, remove, or inspect a TTL or auto-reconcile policy on a stack — e.g.