npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@pulumi/digitalocean

v4.37.1

Published

A Pulumi package for creating and managing DigitalOcean cloud resources.

Downloads

7,898

Readme

Actions Status Slack NPM version Python version NuGet version PkgGoDev License

DigitalOcean provider

The DigitalOcean resource provider for Pulumi lets you use DigitalOcean resources in your cloud programs. To use this package, please install the Pulumi CLI first.

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/digitalocean

or yarn:

$ yarn add @pulumi/digitalocean

Python

To use from Python, install using pip:

$ pip install pulumi_digitalocean

Go

To use from Go, use go get to grab the latest version of the library

$ go get github.com/pulumi/pulumi-digitalocean/sdk/v4

.NET

To use from .NET, install using dotnet add package:

$ dotnet add package Pulumi.Digitalocean

Configuration

The following configuration points are available:

  • digitalocean:token - (Required) This is the DO API token. Alternatively, this can also be specified using environment variables, ordered by precedence, DIGITALOCEAN_TOKEN or DIGITALOCEAN_ACCESS_TOKEN.
  • digitalocean:spacesAccessId - (Optional) The access key ID used for Spaces API operations. May be set via the SPACES_ACCESS_KEY_ID environment variable.
  • digitalocean:spacesSecretKey - (Optional) The secret key used for Spaces API operations. May be set via the SPACES_SECRET_ACCESS_KEY environment variable.
  • digitalocean:apiEndpoint - (Optional) This can be used to override the base URL for DigitalOcean API requests. May be set via the DIGITALOCEAN_API_URL environment variable. Default is https://api.digitalocean.com.

Concepts

The @pulumi/digitalocean package provides a strongly-typed means to create cloud applications that create and interact closely with DigitalOcean resources. Resources are exposed for the entirety of DigitalOcean resources and their properties, including (but not limited to), 'droplet', 'floatingIp', 'firewalls', etc. Many convenience APIs have also been added to make development easier and to help avoid common mistakes, and to get stronger typing.

Reference

For further information, please visit the DigitalOcean provider docs or for detailed reference documentation, please visit the API docs.