This release is a pre-release and may not be stable for production use.
Pulumi Service Provider
A Pulumi Resource Provider for The Pulumi Service.
The Pulumi Service Provider is built on top of the Pulumi Service REST API which is another feature available to our customers to programmatically configuring the Pulumi Service. The Pulumi Service REST API includes functionality to interact with and manipulate any kind of metadata managed by Pulumi. That includes Projects and Stacks, Previews and Updates, Organizations and Audit Logs. We have already seen Cloud Engineering teams using the Pulumi REST API to build all sorts of custom functionality. These new capabilities are especially powerful when used in combination with the Automation API.
Supported Resources
- Webhooks
- Teams
- You can grant a team access to stacks via the
TeamStackPermissionresource
- You can grant a team access to stacks via the
- StackTags
- AccessTokens
For reference documentation, visit the Pulumi Service API Documentation on the Pulumi Registry
Installing
This package is available in many languages in the standard packaging formats.
Node.js (Java/TypeScript)
To use from JavaScript or TypeScript in Node.js, install using either npm:
$ npm install @pulumi/pulumiservice
or yarn:
$ yarn add @pulumi/pulumiservice
Python
To use from Python, install using pip:
$ pip install pulumi_pulumiservice
Go
To use from Go, use go get to grab the latest version of the library
$ go get github.com/pulumi/pulumi-pulumiservice/sdk/go
.NET
To use from .NET, install using dotnet add package:
$ dotnet add package Pulumi.PulumiService
Setup
Ensure that you have ran pulumi login. Run pulumi whoami to verify that you are logged in.
Configuration Options
Use pulumi config set pulumiservice:<option> or pass options to the constructor of new pulumiservice.Provider.
| Option | Environment Variable Name | Required/Optional | Description |
|---|---|---|---|
accessToken |
PULUMI_ACCESS_TOKEN |
Optional | Overrides Pulumi Service Access Tokens |
apiUrl |
PULUMI_BACKEND_URL |
Optional | Allows overriding default Pulumi Service API URL for self hosted customers. |
Examples
import * as aws from "@pulumi/awsx"
import * as pulumi from "@pulumi/pulumi";
import * as service from "@pulumi/pulumiservice";
const team = new service.Team("team", {
name: "pulumi-service-team",
displayName: "Pulumi Service",
description: "The Pulumi Service Team",
organizationName: "pulumi",
teamType: "pulumi",
members: [
"piers",
"bryce",
"casey"
"evan",
"devon",
"meagan"
"myles",
"steve"
],
});
export const members = team.members;
Check out the examples/ directory for more examples.
1 maintainer
Metadata
1 maintainer
Release files for pulumi-pulumiservice 0.14.1a1700170326
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 | Actions |
|---|---|---|---|---|
| pulumi_pulumiservice-0.14.1a1700170326.tar.gz | 20.0 kB | Without provenance | Details for pulumi_pulumiservice-0.14.1a1700170326.tar.gz |
Release files / pulumi_pulumiservice-0.14.1a1700170326.tar.gz
| Download URL | pulumi_pulumiservice-0.14.1a1700170326.tar.gz |
|---|---|
| Size | 20.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aadebd743e6ae84478fd4ad2474c3e7ac8b81131b95a03a992d63aa9de1c1f88
|
|
BLAKE2b-256 checksum How to use checksums |
190e328ff1affb1b43c00f4675459fc34aae8ee4c231f81f6bb8651b96a1146d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.17
|
Security for pulumi-pulumiservice 0.14.1a1700170326
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
