This release is a pre-release and may not be stable for production use.
Pulumi Native Provider Boilerplate
This repository is a boilerplate showing how to create and locally test a native Pulumi provider (with examples of both CustomResource and ComponentResource resource types).
Authoring a Pulumi Native Provider
This boilerplate creates a working Pulumi-owned provider named provider-boilerplate.
It implements a random number generator that you can build and test out for yourself and then replace the Random code with code specific to your provider.
Prerequisites
You will need to ensure the following tools are installed and present in your $PATH:
pulumictl- Go 1.21 or 1.latest
- NodeJS 14.x. We recommend using nvm to manage NodeJS installations.
- Yarn
- TypeScript
- Python (called as
python3). For recent versions of MacOS, the system-installed version is fine. - .NET
Build & test the boilerplate provider
- Run
make build installto build and install the provider. - Run
make gen_examplesto generate the example programs inexamples/off of the sourceexamples/yamlexample program. - Run
make upto run the example program inexamples/yaml. - Run
make downto tear down the example program.
Creating a new provider repository
Pulumi offers this repository as a GitHub template repository for convenience. From this repository:
- Click "Use this template".
- Set the following options:
- Owner: pulumi
- Repository name: pulumi-provider-boilerplate (replace "provider-boilerplate" with the name of your provider)
- Description: Pulumi provider for xyz
- Repository type: Public
- Clone the generated repository.
From the templated repository:
-
Run the following command to update files to use the name of your provider (third-party: use your GitHub organization/username):
make prepare NAME=foo ORG=myorg REPOSITORY=github.com/myorg/pulumi-foo
This will do the following:
- rename folders in
provider/cmdtopulumi-resource-{NAME} - replace dependencies in
provider/go.modto reflect your repository name - find and replace all instances of
provider-boilerplatewith theNAMEof your provider. - find and replace all instances of the boilerplate
abcwith theORGof your provider. - replace all instances of the
github.com/pulumi/pulumi-provider-boilerplaterepository with theREPOSITORYlocation
- rename folders in
Build the provider and install the plugin
$ make build install
This will:
- Create the SDK codegen binary and place it in a
./binfolder (gitignored) - Create the provider binary and place it in the
./binfolder (gitignored) - Generate the dotnet, Go, Node, and Python SDKs and place them in the
./sdkfolder - Install the provider on your machine.
Test against the example
$ cd examples/simple
$ yarn link @pulumi/provider-boilerplate
$ yarn install
$ pulumi stack init test
$ pulumi up
Now that you have completed all of the above steps, you have a working provider that generates a random string for you.
A brief repository overview
You now have:
- A
provider/folder containing the building and implementation logic.cmd/pulumi-resource-provider-boilerplate/main.go- holds the provider's sample implementation logic.
Makefile- targets to help with building and publishing the provider. Runmake ci-mgmtto regenerate CI workflows.sdk- holds the generated code libraries created bypulumi gen-sdk.examplesa folder of Pulumi programs to try locally and/or use in CI.- A
Makefileand thisREADME.
Additional Details
This repository depends on the pulumi-go-provider library. For more details on building providers, please check the Pulumi Go Provider docs.
Build Examples
Create an example program using the resources defined in your provider, and place it in the examples/ folder.
You can now repeat the steps for build, install, and test.
Configuring CI and releases
- Follow the instructions laid out in the deployment templates.
References
Other resources/examples for implementing providers:
1 maintainer
Metadata
1 maintainer
Release files for pulumi-provider-boilerplate 0.1.0a1792088514
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pulumi_provider_boilerplate-0.1.0a1792088514.tar.gz | 11.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pulumi_provider_boilerplate-0.1.0a1792088514-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.1 kB
Release files / pulumi_provider_boilerplate-0.1.0a1792088514.tar.gz
| Download URL | pulumi_provider_boilerplate-0.1.0a1792088514.tar.gz |
|---|---|
| Size | 11.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f4259ab1997e8f1e1c14cd49013899c89a400f3d13b56d90438f60c1483da95a
|
|
BLAKE2b-256 checksum How to use checksums |
6a6357656aee1f7f94a1d4f6e736f0a636cdc699aff9a43205c5341bed69ae40
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.15
|
Release files / pulumi_provider_boilerplate-0.1.0a1792088514-py3-none-any.whl
| Download URL | pulumi_provider_boilerplate-0.1.0a1792088514-py3-none-any.whl |
|---|---|
| Size | 13.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5b0f18ee9faa8b4504b0054c049f213e378aab9e1c04674f4ae30e0a80ebd005
|
|
BLAKE2b-256 checksum How to use checksums |
bac550cd6fe3010ecc59d6e4a2d27b9f035184540c68ae5673d8560049161621
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.15
|
Security for pulumi-provider-boilerplate 0.1.0a1792088514
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
