pulumi package gen-sdk | CLI commands

Generate SDK(s) from a package or schema

Synopsis

Generate SDK(s) from a package or schema.

<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 gen-sdk <schema-source> [flags] [--] [provider-parameter]...

Options

      --extension string   Add an extension layered onto a base provider rather than a replacement. The value is the extension's provider-defined parameters as one shell-quoted string, e.g. --extension "key=value ..."
  -h, --help               help for gen-sdk
      --language string    The SDK language to generate: [nodejs|python|go|dotnet|java|all] (default "all")
      --local              Generate an SDK appropriate for local usage
  -o, --out string         The directory to write the SDK to (default "./sdk")
      --server string      A URL to download the plugin from. When set, the provider argument is used as the plugin name directly and no package resolution is performed.
      --version string     The provider plugin version to generate the SDK for

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
      --otel-traces string           Export OpenTelemetry traces to the specified endpoint. Use file:// for local JSON files, grpc:// or https:// for remote collectors
      --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

• pulumi package - Work with Pulumi packages