What it does

This action executes DigitalOcean CLI commands. The doctl makes it easy to create and manage your DigitalOcean integration directly from the terminal. It’s an essential part of using DigitalOcean.

How it works

The action launches a container with preinstalled DigitalOcean CLI. Once launched, it’s already authorized against provided in the action settings of DigitalOcean account. The container has mounted pipeline filesystem which contains pulled repository.

The action uses Buddy’s OAuth integration with a DigitalOcean account.

Action preview


DigitalOcean Action Features

  • Directories with unversioned files (e.g. uploaded manually) will not be deleted from the server if they are deleted in the repository
  • The first execution deploys everything from scratch by default. If you have legacy files on the server, you can provide the Current Revision in the pipeline settings
  • If you roll back by selecting a previously deployed revision, the action will deploy what is necessary to revert the site to the previous state
  • You can provide the URL of the target server in the pipeline settings so it can be easily opened in a browser from the pipelines list
  • Poor & dropped connections are handled by automatic retries. The retries will continue in case the connection drops
  • The tool supports multithreading to speed up deployments
  • If several actions are connecting to the same server, use Environment Variables to manage user & password credentials instead of providing fixed values in the inputs
  • Once correct login details are provided, it is possible to browse the remote server and select the Remote path (target path for the deployments) from Buddy’s UI instead of typing it manually
  • Sometimes it helps to select the passive mode for the connection, e.g. when the target server is behind a firewall or the connection isn't stable enough
  • Buddy supports passwords, SSH keys, and Buddy's SSH keys as a means of authentication. Passphrases are supported, too
  • You can define SSH keys as ENV VARs and select them in the action details for authentication

Heroku CLI Action Features

  • The commands support Environment Variables
  • The field Run commands supports multiple commands (one per line), piping commands together, or splitting a single command into multiple lines with (backslash) at the end of each line
  • The action can be configured in YAML mode. See DigitalOcean CLI YAML parameters and DigitalOcean CLI YAML config example
  • Buddy's DigitalOcean CLI API is supported
  • The action supports conditional execution: it can be run on each execution, only if there are changes in the repository or specific paths since last execution or if an environment variable has a specific value
  • Optionally it’s possible to select Heroku application using the action UI, in that case parameter --app is not needed
  • The commands are executed in the context of the pipeline’s filesystem, it means that if a command creates a file, it will stay in the filesystem
  • It’s possible to get data from Heroku and pass it to settable environment variables which can be later used by the next actions in the pipeline
  • Action is marked as failed when a command exits with non-zero value
  • Error handling: you can either stop the execution, mark action and pipeline as failed or proceed the execution, mark action as warning and jump to the next action

More about DigitalOcean CLI

More about DigitalOcean CLI

DigitalOcean CLI

Do more with DigitalOcean CLI

Buddy allows you to instantly connect DigitalOcean CLI with 100+ actions to automate your development and build better apps faster.

1 - 9 (of 137)