1. Docs
  2. Pulumi CLI
  3. Commands
  4. pulumi package get-schema

pulumi package get-schema

    Get the schema.json from a package


    Get the schema.json from a package.

    <schema_source> can be a package name or the path to a plugin binary or folder. If a folder either the plugin binary must match the folder name (e.g. ‘aws’ and ‘pulumi-resource-aws’) or it must have a PulumiPlugin.yaml file specifying the runtime to use.

    pulumi package get-schema <schema_source> [provider parameters] [flags]


      -h, --help   help for get-schema

    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


    Auto generated by spf13/cobra on 13-Jun-2024
      Introducing Pulumi Copilot - Intelligent Cloud Management