1. Docs
  2. Pulumi IaC
  3. Pulumi CLI
  4. Commands
  5. pulumi policy new

pulumi policy new

    Create a new Pulumi Policy Pack

    Synopsis

    Create a new Pulumi Policy Pack from a template.

    To create a Policy Pack from a specific template, pass the template name (such as aws-typescript or azure-python). If no template name is provided, a list of suggested templates will be presented which can be selected interactively.

    Once you’re done authoring the Policy Pack, you will need to publish the pack to your organization. Only organization administrators can publish a Policy Pack.

    pulumi policy new [template|url] [flags]
    

    Options

          --dir string      The location to place the generated Policy Pack; if not specified, the current directory is used
      -f, --force           Forces content to be generated even if it would change existing files
      -g, --generate-only   Generate the Policy Pack only; do not install dependencies
      -h, --help            help for new
      -o, --offline         Use locally cached templates without making any network requests
    

    Options inherited from parent commands

          --color string                 Colorize output. Choices are: always, never, raw, auto (default "auto")
      -C, --cwd string                   Run pulumi as if it had been started in another directory
          --disable-integrity-checking   Disable integrity checking of checkpoint files
      -e, --emoji                        Enable emojis in the output
      -Q, --fully-qualify-stack-names    Show fully-qualified stack names
          --logflow                      Flow log settings to child processes (like plugins)
          --logtostderr                  Log to stderr instead of to files
          --memprofilerate int           Enable more precise (and expensive) memory allocation profiles by setting runtime.MemProfileRate
          --non-interactive              Disable interactive mode for all commands
          --profiling string             Emit CPU and memory profiles and an execution trace to '[filename].[pid].{cpu,mem,trace}', respectively
          --tracing file:                Emit tracing to the specified endpoint. Use the file: scheme to write tracing data to a local file
      -v, --verbose int                  Enable verbose logging (e.g., v=3); anything >3 is very verbose
    

    SEE ALSO

    Auto generated by spf13/cobra on 8-Oct-2024
      PulumiUP 2024. Watch On Demand.