Skip to main content

Pulumi Native Provider for Render

Render is a unified cloud to build and run all your apps and websites with free TLS certificates, a global CDN, DDoS protection, private networks, and auto deploys from Git.

This provider was generated using pulschema and pulumi-provider-framework.

Package SDKs

Using The Provider

You'll need an API key. Follow Render's docs for creating one. Then set the API key as a secret with pulumi config set --secret render:apiKey.

Importing Existing Resources

Import IDs should satisfy all ID segments in the GET endpoint for the resource you are importing. The IDs required in the path should be separated by /. Locate the GET endpoint in the OpenAPI spec.

For example, to read a custom domain, the path in the OpenAPI spec is: GET /services/{serviceId}/custom-domains/{customDomainIdOrName}.

Thus, the pulumi import command to run is:

# The type render:services:CustomDomain can be easily found by using your IDEs
# Go To Definition functionality for the resource and looking at the type
# property defined in the custom resource's class definition.
pulumi import render:services:CustomDomain {resourceName} /{serviceId}/{customDomainIdOrName}

Alternatively, you can also import using the import Pulumi resource option. Run pulumi up to import the resource into your stack's state. Once imported, you should remove the import resource option.

const myCustomDomain = new render.services.CustomDomain(
    "myCustomDomain",
    { name: "www.somedomain.com", serviceId: staticSite.id },
    {
        protect: true,
        import: `/srv-xxxxxxxxxxxxxxx/www.somedomain.com`,
    },
);

Refer to the Pulumi docs for importing a resource.

Releasing A New Version

:info: Switch to the main branch first and get the latest git pull origin main && git fetch. Check what the last release tag was.

  1. Regular releases should just increment the patch version unless a minor or a major (breaking changes) version bump is warranted.

  2. Update the CHANGELOG.md with notes about what will be included in this release.

  3. Commit the changelog with git commit -am "vX.Y.Z" or something similar and push git push origin main.

  4. Tag the commit with the release version by running

    git tag vX.Y.Z
    git tag sdk/vX.Y.Z
    
  5. Push the tags.

    git push --tags
    

Metadata

Release files for pulumi-render 0.6.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pulumi-render 0.6.0
File Size Uploaded
pulumi_render-0.6.0.tar.gz 166.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for pulumi-render 0.6.0
File Interpreter ABI Platform
pulumi_render-0.6.0-py3-none-any.whl Python 3 none any Details

Total release size: 477.5 kB

Release files / pulumi_render-0.6.0.tar.gz

Download URL pulumi_render-0.6.0.tar.gz
Size 166.7 kB
Tags Source
SHA-256 checksum
How to use checksums
53dedf9b8078a4f3b072b534ba38246b3f0299083cdf999ee3a2e2e9d06d0c4e
BLAKE2b-256 checksum
How to use checksums
c7d662e0dedb92516dbb12f775de5e77e745178a11055efbd6e502143feb268f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release files / pulumi_render-0.6.0-py3-none-any.whl

Download URL pulumi_render-0.6.0-py3-none-any.whl
Size 310.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
af04a3f310098ef1a28e0d144009940bfae55b427b26a19ec25e18562a2c29fb
BLAKE2b-256 checksum
How to use checksums
335bd572f1a03a77eb1570f1c97097ccf404027a3a0180ab2a8e8c3f0954f928
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.6.0 This release

2 release files

0.5.5

2 release files

0.5.4

2 release files

0.5.3

2 release files

0.4.3

2 release files

0.4.2

2 release files

0.4.1

2 release files

0.3.11

2 release files

0.3.10

2 release files

0.3.9

2 release files

0.3.8

2 release files

0.3.7

2 release files

0.3.6

2 release files

0.3.5

2 release files

0.3.4

2 release files

0.3.2

2 release files

0.3.1

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.1

2 release files

0.0.47

1 release file

0.0.46

1 release file

0.0.45

1 release file

0.0.44

1 release file

0.0.43

1 release file

0.0.42

1 release file

0.0.41

1 release file

0.0.40

1 release file

0.0.39

1 release file

0.0.37

1 release file

0.0.36

1 release file

0.0.35

1 release file

0.0.34

1 release file

0.0.33

1 release file

0.0.32

1 release file

0.0.31

1 release file

0.0.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page