pltf generate

Generate Terraform from an Environment or Service spec (auto-detects kind)

Synopsis

Read a YAML spec, detect Environment vs Service, and render Terraform with the proper remote state, providers, locals, secrets, and module wiring. Uses embedded modules by default; can override modules root and output directory.

pltf generate [flags]

Examples

  pltf generate -f env.yaml -e dev
  pltf generate -f service.yaml -e prod -m ./modules -o .pltf/my-env/my-svc/env/prod

Options

  -e, --env string        Environment key to render (dev, prod, etc.); required for both env and service specs
  -f, --file string       Path to the Environment or Service YAML file (default "env.yaml")
  -h, --help              help for generate
  -m, --modules string    Root directory containing module type folders with module.yaml metadata; defaults to embedded modules bundle
  -o, --out string        Output directory for generated Terraform (defaults based on kind: .pltf/<env_name>/env/<env> or .pltf/<env_name>/<service>/env/<env>)
  -v, --var stringArray   Override variable as key=value; merges over vars and supports bool/int/JSON/list parsing. Can be repeated for multiple overrides.

Options inherited from parent commands

      --telemetry   Enable anonymous telemetry (usage metrics). Currently a stub/no-op unless enabled.
  -V, --verbose     Enable verbose logging

SEE ALSO

  • pltf - Platform toolkit for validating and generating Terraform stacks
Auto generated by spf13/cobra on 21-Dec-2025