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

• Node.js: https://www.npmjs.com/package/@cloudyskysoftware/pulumi-render
• Python: https://pypi.org/project/pulumi-render/
• .NET: https://www.nuget.org/packages/Pulumi.Render
• Go: import github.com/cloudyskysoftware/pulumi-render/sdk/go/render

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