Memcached: 1. Create an access token and store it as a CI secret
This documentation is part of the GitHub Actions & GitLab CI guide. View the full guide here: Spin up a real Memcached service from your GitHub Actions or GitLab CI pipeline, run your tests against it, and tear it down automatically.
Welcome to the Stackhero documentation
Stackhero provides a fully managed Memcached cloud that makes application caching simple, secure, and high-performing.
- Apply updates in seconds with one click.
- Get consistent performance and strong security on a private, dedicated infrastructure.
Free up your time and focus on building. Stackhero's Memcached cloud hosting is up and running in about 5 minutes.
To enable the CLI to work non-interactively, you will need an access token (format: usr-xxxxxx:tokenId). You only need to create this token once and then add it to your CI pipeline as a secure, encrypted secret.
- 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.
- For GitHub Actions: In your repository, go to Settings > Secrets and variables > Actions > New repository secret, and enter the token as
STACKHERO_TOKEN. - For GitLab CI: In your project, go to Settings > CI/CD > Variables > Add variable, set the key to
STACKHERO_TOKEN, and check Masked (and Protected if your CI runs only on protected branches).
Do not include your access token directly in your pipeline YAML file. If it is present in YAML, it could be exposed to anyone with repository access and may appear in build logs. Storing it as a CI secret keeps it encrypted and masked, ensuring your token stays secure.