DigitalOcean: Installation & Configuration
The Pulumi DigitalOcean provider uses the DigitalOcean SDK to manage and provision resources.
Installation
The DigitalOcean provider is available as a package in all Pulumi languages:
- JavaScript/TypeScript:
@pulumi/digitalocean
- Python:
pulumi-digitalocean
- Go:
github.com/pulumi/pulumi-digitalocean/sdk/v4/go/digitalocean
- .NET:
Pulumi.DigitalOcean
- Java:
com.pulumi/digitalocean
Configuring Credentials
Pulumi relies on the DigitalOcean SDK to authenticate requests from your computer to DigitalOcean. Your credentials are never sent to pulumi.com. The Pulumi DigitalOcean Provider needs to be configured with DigitalOcean credentials before it can be used to create resources.
Once the credentials are obtained, there are two ways to communicate your authorization tokens to Pulumi:
Set the environment variable
DIGITALOCEAN_TOKEN
:$ export DIGITALOCEAN_TOKEN=XXXXXXXXXXXXXX
Set them using configuration, if you prefer that they be stored alongside your Pulumi stack for easy multi-user access:
$ pulumi config set digitalocean:token XXXXXXXXXXXXXX --secret
Remember to pass --secret
when setting token
so that it is properly encrypted.
Spaces API Credentials
To create Space Buckets with Pulumi, you will need an access key for the Spaces API. Once you’ve created a Spaces access key, you can set them in one of two ways for Pulumi:
Set them as environment variables:
$ export SPACES_ACCESS_KEY_ID=XXXXXXXXXXXXXX $ export SPACES_SECRET_ACCESS_KEY=XXXXXXXXXXXXXX
Set them using configuration, if you prefer that they be stored alongside your Pulumi stack for easy multi-user access:
$ pulumi config set digitalocean:spaces_access_id XXXXXXXXXXXXXX $ pulumi config set digitalocean:spaces_secret_key XXXXXXXXXXXXXX --secret
Remember to pass --secret
when setting spaces_secret_key
so that it is properly encrypted.