https://github.com/stackitcloud/stackit-cli
A command-line interface to manage STACKIT resources
https://github.com/stackitcloud/stackit-cli
cli cloud stackit stackit-cloud
Last synced: 7 days ago
JSON representation
A command-line interface to manage STACKIT resources
- Host: GitHub
- URL: https://github.com/stackitcloud/stackit-cli
- Owner: stackitcloud
- License: apache-2.0
- Created: 2023-10-02T08:18:09.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2026-04-15T11:47:20.000Z (12 days ago)
- Last Synced: 2026-04-15T12:31:40.252Z (12 days ago)
- Topics: cli, cloud, stackit, stackit-cloud
- Language: Go
- Homepage: https://www.stackit.de/en
- Size: 8.03 MB
- Stars: 148
- Watchers: 5
- Forks: 37
- Open Issues: 26
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
- Codeowners: .github/CODEOWNERS
- Security: SECURITY.md
- Notice: NOTICE.txt
Awesome Lists containing this project
README
# STACKIT CLI
[](https://goreportcard.com/report/github.com/stackitcloud/stackit-cli)  [](https://www.apache.org/licenses/LICENSE-2.0)
Welcome to the STACKIT CLI, a command-line interface for [STACKIT - The sovereign cloud for Europe](https://www.stackit.de/en).
The STACKIT CLI allows you to manage your STACKIT services and resources as well as perform operations using the command-line or in scripts or automation, such as:
- Projects, including permissions
- STACKIT Kubernetes Engine clusters
- Servers
- DNS zones and record-sets
- Databases such as PostgreSQL Flex, MongoDB Flex and SQLServer Flex
Your feedback is appreciated!
Feel free to open [GitHub issues](https://github.com/stackitcloud/stackit-cli) to provide feature requests and bug reports.
## Installation
Please refer to our [installation guide](./INSTALLATION.md) for instructions on how to install and get started using the STACKIT CLI.
## Documentation
There is some [documentation](./docs/stackit.md) available in the markdown format inside the `docs` directory of the repository.
## Usage
A typical command is structured as:
```
stackit [OPTION FLAGS]
```
- `` can be the name of a service, such as `dns` or `mongodbflex`, or other groups for additional functionality, such as `config` to configure the CLI or `auth` to authenticate.
- `` should be the name (singular form) of a service resource, when `` is the name of a service. Examples: `zone`, `instance`.
- `` is a command associated to the innermost group. Usually it's an action for the resource in question, such as `list` (to show all resources of the given type) or the CRUD operations `create`, `describe`, `update` and `delete`.
- `` is required by some commands to specify a resource identifier. Examples: `stackit dns zone delete ZONE_ID`, `stackit ske cluster create CLUSTER_NAME`.
- `` is a list of inputs necessary to execute the command, in the format `--[flag]` or `--[flag] [value]`. Some are required, while others are optional.
- `[OPTION FLAGS]` is a set of optional settings that modify the command's execution context. Examples: `--output-format=json` changes the format of the output to JSON, `--assume-yes` skips confirmation prompts.
Examples:
- `stackit ske cluster describe my-cluster --project-id xxx --output-format json`
- `stackit mongodbflex instance create --name my-instance --cpu 1 --ram 4 --acl 0.0.0.0/0 --assume-yes`
- `stackit dns zone delete my-zone`
Some commands are implemented at the root, group or subgroup level:
- `stackit config` to define variables to be used in future commands.
- `stackit ske enable` to enable the SKE engine on your project.
Help is available for any command by specifying the special flag `--help` (or simply `-h`):
- `stackit --help`
- `stackit -h`
- `stackit --help`
- `stackit --help`
- `stackit --help`
## Available services
Below you can find a list of the STACKIT services already available in the CLI (along with their respective command names) and the ones that are currently planned to be integrated.
| Service | CLI Commands | Status |
|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|
| Application Load Balancer | `beta alb` | :white_check_mark: (beta) |
| Authorization | `project`, `organization` | :white_check_mark: |
| DNS | `dns` | :white_check_mark: |
| Edge Cloud | `beta edge-cloud` | :white_check_mark: (beta) |
| Git | `git` | :white_check_mark: |
| Infrastructure as a Service (IaaS) | `affinity-group`
`image`
`key-pair`
`network`
`network-area`
`network-interface`
`public-ip`
`quota`
`security-group`
`server`
`volume` | :white_check_mark: |
| Intake | `beta intake` | :white_check_mark: (beta) |
| Key Management Service (KMS) | `beta kms` | :white_check_mark: (beta) |
| Kubernetes Engine (SKE) | `ske` | :white_check_mark: |
| Load Balancer | `load-balancer` | :white_check_mark: |
| LogMe | `logme` | :white_check_mark: |
| MariaDB | `mariadb` | :white_check_mark: |
| MongoDB Flex | `mongodbflex` | :white_check_mark: |
| Observability | `observability` | :white_check_mark: |
| Object Storage | `object-storage` | :white_check_mark: |
| OpenSearch | `opensearch` | :white_check_mark: |
| PostgreSQL Flex | `postgresflex` | :white_check_mark: |
| RabbitMQ | `rabbitmq` | :white_check_mark: |
| Redis | `redis` | :white_check_mark: |
| Resource Manager | `project` | :white_check_mark: |
| Secrets Manager | `secrets-manager` | :white_check_mark: |
| Server Backup Management | `server backup` | :white_check_mark: |
| Server Command (Run Command) | `server command` | :white_check_mark: |
| Service Account | `service-account` | :white_check_mark: |
| SQLServer Flex | `beta sqlserverflex` | :white_check_mark: (beta) |
| File Storage (SFS) | `beta sfs` | :white_check_mark: (beta) |
## Authentication
Most of the commands will require you to be authenticated. Currently, it's possible to authenticate with your personal user or with a service account.
After successful authentication, the CLI stores credentials in your OS keychain. You won't need to log in again for the duration of your session, which is 2h by default but configurable by providing the `--session-time-limit` flag on the `config set` command (see [Configuration](#configuration)).
### Login with a personal user account
To authenticate as a user, run the command below and follow the steps in your browser.
```bash
stackit auth login
```
### Activate a service account
To authenticate using a service account, run:
```bash
stackit auth activate-service-account
```
For more details on how to set up authentication using a service account, check our [authentication guide](./AUTHENTICATION.md).
## Configuration
You can configure the CLI using the command:
```bash
stackit config
```
The configuration is saved in a file. The file's location varies depending on the operating system:
- Unix - `$XDG_CONFIG_HOME/stackit/cli-config.json`
- MacOS - `$HOME/Library/Application Support/stackit/cli-config.json`
- Windows - `%AppData%\stackit\cli-config.json`
The configuration options apply to all commands and can be set using the `stackit config set` command. For example, you can set a default `project-id` by running:
```bash
stackit config set --project-id xxxx-xxxx-xxxxx
```
To remove it, you can run:
```bash
stackit config unset --project-id
```
Run the `config set` command with the flag `--help` to get a list of all the available configuration options.
You can look up your current configuration by checking the configuration file or by running:
```bash
stackit config list
```
You can also edit the configuration file manually.
## Customization
### Pager
To specify a custom pager, use the `PAGER` environment variable.
If the variable is not set, STACKIT CLI uses the `less` as default pager.
When using `less` as a pager, STACKIT CLI will automatically pass following options
- -F, --quit-if-one-screen - Less will automatically exit if the entire file can be displayed on the first screen.
- -S, --chop-long-lines - Lines longer than the screen width will be chopped rather than being folded.
- -w, --hilite-unread - Temporarily highlights the first "new" line after a forward movement of a full page.
- -R, --RAW-CONTROL-CHARS - ANSI color and style sequences will be interpreted.
> These options will not be added automatically if a custom pager is defined.
>
> In that case, users can define the parameters by using the specific environment variable required by the `PAGER` (if supported).
> For example, if user sets the `PAGER` environment variable to `less` and would like to pass some arguments, `LESS` environment variable must be used as following:
> export PAGER="less"
>
> export LESS="-R"
## Autocompletion
If you wish to set up command autocompletion in your shell for the STACKIT CLI, please refer to our [autocompletion guide](./AUTOCOMPLETION.md).
## Reporting issues
If you encounter any issues or have suggestions for improvements, please open an issue in the [repository](https://github.com/stackitcloud/stackit-cli/issues).
## Contribute
Your contribution is welcome! For more details on how to contribute, refer to our [contribution guide](./CONTRIBUTION.md).
## Release creation
See the [release documentation](./RELEASE.md) for further information.
## License
Apache 2.0
## Useful Links
- [STACKIT Portal](https://portal.stackit.cloud/)
- [STACKIT](https://www.stackit.de/en/)
- [STACKIT Docs](https://docs.stackit.cloud/)
- [STACKIT Terraform Provider](https://registry.terraform.io/providers/stackitcloud/stackit/latest/docs)