DigitalOcean Waypoint Plugin

This is a prototype DigitalOcean Waypoint plugin. It currently has very basic support for deploying a Docker image from a DigitalOcean Container Registry to DigitalOcean App Platform. It should be considered experimental.

See the Waypoint documentation on installing external plugins for more detail on installing external plugins.

Configuration

A Waypoint configuration of this might look like:

project = "example-nodejs"

app "example-nodejs" {
  build {
    use "pack" {}
    registry {
        use "docker" {
          image = "registry.digitalocean.com/<username>/example-nodejs"
          tag   = "latest"
        }
    }
 }

  deploy {
    use "digitalocean" {
    }
  }
}

The following configuration options are supported. They are all optional.

• access_token - Required if DIGITALOCEAN_ACCESS_TOKEN is not set
• name - Defaults to the app's name
• region - Defaults to nearest region
• instance_size_slug - Defaults to basic-xxs
• instance_count - Default to 1
• http_port - Default to 8080
• path - Default to /

Development

Building

To build the plugin, run:

make

This will regenerate the protos and build binaries for multiple platforms.

Installation

To install the binary to ${HOME}/.config/waypoint/plugins/ run:

make install

Building with Docker

To build plugins for release you can use the build-docker Makefile target, this will build your plugin for all architectures and create zipped artifacts which can be uploaded to an artifact manager such as GitHub releases.

The built artifacts will be output in the ./releases folder.

Building and releasing with GitHub Actions

When cloning the template a default GitHub Action is created at the path .github/workflows/build-plugin.yaml. You can use this action to automatically build and release your plugin.

The action has two main phases:

1. Build - This phase builds the plugin binaries for all the supported architectures. It is triggered when pushing to a branch or on pull requests.
2. Release - This phase creates a new GitHub release containing the built plugin. It is triggered when pushing tags which starting with v, for example v0.1.0.