Skip to main content

Pulumi Native Provider for Tailscale (Preview)

Tailscale connects your team's devices and development environments for easy access to remote resources.

ℹ️ This provider uses Tailscale's API directly.

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

Why Is This Called Tailscale Native?

Despite the fact that all Pulumi providers created by Cloudy Sky Software being "native" Pulumi providers, by default, there is a prior Pulumi provider for Tailscale, albeit a TF-bridged one. So this provider had to be renamed to avoid naming conflicts, specifically in language package registries such as PyPi and Nuget where the packages are not namespaced under an organization or user unlike npm.

Package SDKs

Using The Provider

OAuth2 Client

A quote from Tailscale's own docs:

OAuth clients provide a framework for delegated and scoped access to the Tailscale API. An OAuth client creates access tokens for scoped API access, instead of using a fully-permitted access token which expires after 90 days (or less if the fully-permitted access token has a shorter expiry). OAuth clients support the principle of least privilege by allowing fine-grained control on the access granted to the client using scopes, unlike a fully-permitted access token which grants full access to the Tailscale API.

  • Create an OAuth client on https://login.tailscale.com/admin/settings/oauth.
  • Grant the appropriate scopes (permissions) to the client.
  • Copy the client ID and secret.
  • Set the client ID with pulumi config set tailscale-native:clientId <clientID>.
  • Set the client secret with pulumi config set --secret tailscale-native:clientSecret <clientSecret>.
  • Optional: Remove the API key config tailscale-native:apiKey from your stack config if you previously used that method of auth.

Read the full official docs at https://tailscale.com/kb/1215/oauth-clients/.

API Key

You'll need an API access token (aka API key). Follow Tailscale's docs for creating one or head straight to your tailnet admin console to create one. Then set the API key as a secret with pulumi config set --secret tailscale-native:apiKey.

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-tailscale-native 0.0.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-tailscale-native 0.0.0
File Size Uploaded
pulumi_tailscale_native-0.0.0.tar.gz 31.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for pulumi-tailscale-native 0.0.0
File Interpreter ABI Platform
pulumi_tailscale_native-0.0.0-py3-none-any.whl Python 3 none any Details

Total release size: 86.2 kB

Release files / pulumi_tailscale_native-0.0.0.tar.gz

Download URL pulumi_tailscale_native-0.0.0.tar.gz
Size 31.2 kB
Tags Source
SHA-256 checksum
How to use checksums
f9766d77176a8caaa674a08e5aeb4cfb1f78d5cee2c5b7d331996e2f9a2bbaed
BLAKE2b-256 checksum
How to use checksums
ce94ed657099092cbd8a067f04a580c7e15e8fed128286342414ef4d3b297c90
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 16, 2026.

Transparency log

Release files / pulumi_tailscale_native-0.0.0-py3-none-any.whl

Download URL pulumi_tailscale_native-0.0.0-py3-none-any.whl
Size 55.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
82f7f44094b4fe49000114d1a9c1f1bbd6e6c9685035a76486759015988899ac
BLAKE2b-256 checksum
How to use checksums
0bd91e534eeef91f3f51253385530d4227ea3960bafcce3123918634026aeb18
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 16, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.6

2 release files

0.1.5

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.0.14

1 release file

0.0.13

1 release file

0.0.12

1 release file

0.0.11

1 release file

0.0.10

1 release file

0.0.9

1 release file

0.0.7

1 release file

0.0.6

1 release file

0.0.3

1 release file

This release

0.0.0 This release

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