doctl | official command line interface for the DigitalOcean API | Continuous Deployment library

There are a couple of approaches I can think of:

1. As you mentioned, replacing the create-envfile Action invocation with your own script to dump environment variables to a .env file and adding that as an argument to your appleboy/ssh-action invocation step. I don't see this as a major burden - you could just copy most of the code from here.
2. Keeping the SpicyPizza/create-envfile action step but modifying the output path to a location inside the GitHub Actions runner. Then, scp the env file you just created to your droplet. You can do this with your own subsequent run step or you could use this scp GitHub Action. File changes by separate steps remain in the runner workspace until the end of the job, and subsequent steps see previous steps' changes on the runner's filesystem.

Your question is unclear.

Do you wish to filter the list of snapshots by a given Droplet (ID)?

If so, I suspect you'll want to consider using doctl --output=json to get the doctl command's output as JSON and then use a tool like jq to filter the result.

I created a Droplet and a snapshot and this works:

Well one solution was to change the command to be an absolute path inside my .sh file like so:

Actually, I figured it out. Have to add build-args to the Build and Push part, and remove the env from there.

So instead of:

Relpace

PATH is overridden in your Drone environment variables

It doesn't look like your PATH variable is intended to hold executable paths (PATH: keycloak-svc). I'd recommend using a different name.

If, after changing that environment variable name, you find that /usr/local/bin/ isn't on Drone's PATH, you can add it in the commands section, as described in the Drone docs.

Note:

I thought to look at PATH after finding logs of someone else's failed build and then taking a peek at a change they committed around the same time.

Jeff the following command can be used to update your key doctl auth init --access-token this should update the configs for further use as well. If not check your config.yaml to ensure the token was updated.

When running a Docker container, any arguments you supply on the command line will overwrite the arguments in CMD.

From the CMD documentation:

There can only be one CMD instruction in a Dockerfile. If you list more than one CMD then only the last CMD will take effect.

The main purpose of a CMD is to provide defaults for an executing container. These defaults can include an executable, or they can omit the executable, in which case you must specify an ENTRYPOINT instruction as well.

To set up the server like you are trying to do with CMD, you can create a shell script to run setup and run that in your ENTRYPOINT.

create a file with some name, let's say setup_server.sh, with contents:

In the very next paragraph under the one you linked to it says:

The --access-token flag or DIGITALOCEAN_ACCESS_TOKEN variable are acknowledged

so presumably: