Skip to content

FAQ

Last updated on

  • STACKIT CLI

    How can I set up the STACKIT CLI?

    Refer to the Installation guide for detailed instructions.

    How can I set up configuration options?

    You can set the configuration values by using the stackit config command group.

    Refer to the Configuration section in our GitHub repo for more details.

    Which configuration options can I set in the STACKIT CLI?

    You can set the project ID, verbosity level, session time limit, and multiple custom endpoints. For the full list and the correct syntax, run stackit config set --help.

    What can I do when the installation fails with the error `Failed to connect to GitHub.com`?

    Check your VPN and proxy settings. These services can interfere with the connection to the installation servers by blocking or rerouting the data transfer. Turn them off temporarily and run the installation again. After the installation is complete, turn your VPN and proxy back on.

    Do you support installation packages for Windows?

    Yes. You can install the STACKIT CLI on Windows with the scoop package manager. View the setup guide in the STACKIT CLI GitHub repository.

    Do you check the STACKIT CLI for vulnerabilities?

    Yes, we monitor the repository for vulnerabilities with Snyk. We also check pull requests (PRs) for vulnerabilities and only merge them if they don’t introduce high or critical vulnerabilities.

    Can I save multiple configurations for different projects?

    Yes, you can use profiles to save multiple configurations in the STACKIT CLI. When a profile is not set, the default profile is used. You can see the available commands by calling stackit config profile --help.

    Find more in depth information about Configuration profiles in the GitHub documentation.

    Can I choose which pager to use for command output?

    Yes, you can specify a custom pager using the PAGER environment variable. If the variable isn’t set, the STACKIT CLI uses less as the default pager.

    Why are certain services in beta state?

    The STACKIT CLI includes beta features so you can try features under development early. Because beta features are kept separate, you can test them without changing your stable setup, and your main workflows stay stable.

  • STACKIT Terraform Provider

    How can I set up the STACKIT Terraform Provider?

    Refer to the Installation guide.

    Can I set up a Terraform backend using STACKIT Object Storage?

    Yes, you can configure an S3 backend using STACKIT Object Storage to store the Terraform state.

    More information can be found in the Backend configuration section of our GitHub documentation.

    Can STACKIT Terraform Provider write secrets to Secrets Manager?

    You can use the Vault Provider together with the stackit_secretsmanager_instance.

    For more information, see Using Vault Provider with STACKIT Secrets Manager.

    Are attributes inside nested resource blocks validated?

    No. Terraform doesn’t parse and validate these attributes. For the supported attributes, see the resource documentation in the Terraform Registry.

    Why are certain resources marked as beta?

    The STACKIT Terraform Provider marks resources as beta to support beta features of STACKIT services without risking breaking changes for stable resources. You opt in to beta resources explicitly, so experimental functionality doesn’t affect your existing resources.

    For more information, see the guide Opting into beta resources.

    Can I assign multiple members to a project with the STACKIT Terraform Provider?

    Yes, you can specify a list of members to add to your project. For the syntax, see the Resource Manager project resource in the Terraform Registry.

  • STACKIT Go SDK

    How can I set up the STACKIT Go SDK?

    Refer to the Setup guide.

    Where can I find examples of how to use the SDK?

    You can find examples for services, configuration, and authentication in the code examples on GitHub.

    How do I authenticate to the SDK?

    You authenticate with a service account. The SDK supports two flows:

    • Key flow: Uses a service account key.
    • Workload Identity Federation flow: Uses short-lived tokens from an external OIDC issuer, without static keys.

    Choose the flow that fits your use case. For how the flows work and when to use which, see Service account authentication. For the configuration in the SDK, see the Authentication guide in the GitHub repository.

  • STACKIT Python SDK

    How can I set up the STACKIT Python SDK?

    Refer to the Setup guide.

    Where can I find examples of how to use the SDK?

    You can find examples for services, configuration, and authentication in the code examples on GitHub.

    How do I authenticate to the SDK?

    You authenticate with a service account. The SDK supports two flows:

    • Key flow: Uses a service account key.
    • Workload Identity Federation flow: Uses short-lived tokens from an external OIDC issuer, without static keys.

    Choose the flow that fits your use case. For how the flows work and when to use which, see Service account authentication. For the configuration in the SDK, see the Authentication guide in the GitHub repository.