spacectl
, the Spacelift CLI»
spacectl
is a utility wrapping Spacelift's GraphQL API for easy programmatic access in command-line contexts - either in manual interactive mode (in your local shell), or in a predefined CI pipeline (GitHub actions, CircleCI, Jenkins etc).
Its primary purpose is to help you explore and execute actions inside Spacelift. It provides limited functionality for creating or editing resources. To do that programmatically, you can use the Spacelift Terraform Provider.
Installation»
Officially supported packages»
Officially supported packages are maintained by Spacelift and are the preferred ways to install spacectl
Homebrew»
You can install spacectl
using Homebrew on MacOS or Linux:
1 |
|
Windows»
You can install spacectl
using winget:
1 |
|
or
1 |
|
Docker image»
spacectl
is distributed as a Docker image, which can be used as follows:
1 |
|
Don't forget to add the required environment variables in order to authenticate.
asdf»
1 2 3 |
|
GitHub Release»
Alternatively, spacectl
is distributed through GitHub Releases as a zip file containing a self-contained statically linked executable built from the source in this repository. Binaries can be download directly from the Releases page.
Usage on GitHub Actions»
We have setup-spacectl GitHub Action that can be used to install spacectl
:
1 2 3 4 5 6 7 8 9 10 |
|
Community supported packages»
Disclaimer: These packages are community-maintained, please verify the package integrity yourself before using them to install or update spacectl
.
Arch linux»
Install spacectl-bin
: from the Arch User Repository (AUR):
1 |
|
Please make sure to verify the PKGBUILD
before installing/updating.
Alpine linux»
Install spacectl
from the Alpine Repository (alpine packages):
1 |
|
Please make sure to verify the APKBUILD
before installing/updating.
Quick Start»
Authenticate using spacectl profile login
:
1 2 3 4 5 6 7 |
|
Use spacectl 🚀:
1 2 3 4 |
|
Getting Help»
To list all the commands available, use spacectl help
:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 |
|
To get help about a particular command or subcommand, use the -h
flag:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
|
Example»
The following screencast shows an example of using spacectl to run a one-off task in Spacelift:
Authentication»
spacectl
is designed to work in two different contexts - a non-interactive scripting mode (eg. external CI/CD pipeline) and a local interactive mode, where you type commands into your shell. Because of this, it supports two types of credentials - environment variables and user profiles.
We refer to each method of providing credentials as "credential providers" (like AWS), and details of each method are documented in the following sections.
Authenticating using environment variables»
The CLI supports the following authentication methods via the environment:
spacectl
looks for authentication configurations in the order specified above, and will stop as soon as it finds a valid configuration. For example, if a Spacelift API token is specified, GitHub tokens and Spacelift API keys will be ignored, even if their environment variables are specified.
Spacelift API tokens»
Spacelift API tokens can be specified using the SPACELIFT_API_TOKEN
environment variable. When this variable is found, the CLI ignores all the other authentication environment variables because the token contains all the information needed to authenticate.
NOTE: API tokens are generally short-lived and will need to be re-created often.
GitHub tokens»
GitHub tokens are only available to accounts that use GitHub as their identity provider, but are very convenient for use in GitHub actions. To use a GitHub token, set the following environment variables:
SPACELIFT_API_KEY_ENDPOINT
- the URL to your Spacelift account, for examplehttps://mycorp.app.spacelift.io
.SPACELIFT_API_GITHUB_TOKEN
- a GitHub personal access token.
Spacelift API keys»
To use a Spacelift API key, set the following environment variables:
SPACELIFT_API_KEY_ENDPOINT
- the URL to your Spacelift account, for examplehttps://mycorp.app.spacelift.io
.SPACELIFT_API_KEY_ID
- the ID of your Spacelift API key. Available via the Spacelift application.SPACELIFT_API_KEY_SECRET
- the secret for your API key. Only available when the secret is created.
More information about API authentication can be found at our GraphQL API documentation.
Authenticating using account profiles»
In order to make working with multiple Spacelift accounts easy in interactive scenarios, Spacelift supports account management through the profile
family of commands:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
|
Each of the subcommands requires an account alias, which is a short, user-friendly name for each set of credentials (account profiles). Profiles don't need to be unique - you can have multiple sets of credentials for a single account too.
Account profiles support three authentication methods:
-
GitHub access tokens
-
API keys
-
Login with a browser (API token).
In order to authenticate to your first profile, type in the following (make sure to replace ${MY_ALIAS}
with the actual profile alias):
1 2 |
|
In the next step, you will be asked to choose which authentication method you are going to use. Note that if your account is using SAML-based SSO authentication, then API keys and login with a browser are your only options. After you're done entering credentials, the CLI will validate them against the server, and assuming that they're valid, will persist them in a credentials file in .spacelift/${MY_ALIAS}
. It will also create a symlink in ${HOME}/.spacelift/current
pointing to the current profile.
By default the login process is interactive, however, if that does not fit your workflow, the steps can be predefined using flags, for example:
1 |
|
You can switch between account profiles by using spacectl profile select ${MY_ALIAS}
. What this does behind the scenes is point ${HOME}/.spacelift/current
to the new location. You can also delete stored credentials for a given profile by using the spacectl profile logout ${MY_ALIAS}
command.