RabbitMQ: 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 RabbitMQ service from your GitHub Actions or GitLab CI pipeline, run your tests against it, and automatically tear it down.

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.

Continue reading this guide

  1. Read the full guide: GitHub Actions & GitLab CI
    Launch a real RabbitMQ service from your GitHub Actions or GitLab CI pipeline, run your tests against it, and automatically tear it down
  2. 2. The lifecycle script
  3. 3. Choose the instance size
  4. 4. GitHub Actions
  5. 5. GitLab CI

Other articles for RabbitMQ

  1. Introduction
    Introduction to Stackhero for RabbitMQ
  2. Getting started
    How to use Stackhero for RabbitMQ
  3. Automate with the CLI
    Start RabbitMQ, retrieve its credentials, and modify its configuration programmatically using the Stackhero CLI