InfluxDB: 1. Create an access token and store it as a CI secret

This documentation is part of the GitHub Actions & GitLab CI guide. You can view the complete guide here: Launch a real InfluxDB service from your GitHub Actions or GitLab CI pipeline, run your tests against it, and automatically tear it down.

👋 Welcome to the Stackhero documentation

Stackhero provides a fully managed InfluxDB cloud environment, designed for speed and simplicity:

• Unlimited writes, queries, dashboards, tasks, and buckets.
• Unlimited data retention: keep your metrics for as long as you need.
• Unlimited network and disk transfers, with no hidden limits.
• One-click updates: always benefit from the latest features and fixes.
• Consistent performance and enhanced security on your own private, dedicated infrastructure.

With Stackhero, you can focus on your data and analysis. Deploying InfluxDB cloud hosting only takes a few minutes, with every setup optimised for long-term reliability.

To allow the CLI to work non-interactively, you will need an access token (format: usr-xxxxxx:tokenId). You only need to create this token once, then add it to your CI pipeline as a secure, encrypted secret.

1. Create the token: In your Stackhero dashboard, click your profile picture at the top right, go to Your account, then Access tokens, and click Create token.
2. For GitHub Actions: In your repository, go to Settings > Secrets and variables > Actions > New repository secret, and enter the token as STACKHERO_TOKEN.
3. For GitLab CI: In your project, go to Settings > CI/CD > Variables > Add variable, set the key to STACKHERO_TOKEN, and tick Masked (and Protected if your CI only runs on protected branches).

Never add your access token directly into your pipeline YAML file. If it is present in the YAML, it could be exposed to anyone with repository access and may appear in build logs. Storing it as a CI secret ensures it remains encrypted and masked, keeping your token secure.