little-chef-2593
05/13/2026, 1:58 AMastonishing-architect-11492
05/13/2026, 2:51 PMpluginDownloadURL in the schema to point at the location of the binary.little-chef-2593
05/15/2026, 2:46 AMpulumi package addlittle-chef-2593
05/15/2026, 2:47 AMastonishing-architect-11492
05/15/2026, 8:47 PMpulumi package add <http://github.com/|github.com/><org>/<repo> is the source-based path, not a fetch-from-releases shortcut. For an executable plugin distributed via GitHub releases, point package add at the schema and let pluginDownloadURL handle the binary:
1. In schema.json, set:
"pluginDownloadURL": "<github://api.github.com/><org>/<repo>"
2. Host the schema somewhere reachable (your release assets work) and run:
pulumi package add <https://github.com/><org>/<repo>/releases/download/v0.1.0/schema.json
Pulumi reads the schema to generate the SDK, then uses pluginDownloadURL plus name/version to pull the binary at runtime. The release assets need to follow pulumi-resource-<name>-vX.Y.Z-<os>-<arch>.tar.gz.little-chef-2593
05/19/2026, 3:47 AMlittle-chef-2593
05/23/2026, 7:23 AMschema.json file from private repository. There seem to be no direct support in CLI for that.astonishing-architect-11492
05/27/2026, 3:10 PMpulumi package add doesn’t currently support fetching schema.json from a private GitHub repo. So the schema needs to be either publicly reachable, downloaded locally first and passed as ./schema.json, or served from somewhere the CLI can access directly. The provider binaries themselves can still be private via pluginDownloadURL.