CI/CD and Altostra

Altostra CLI is built for CI/CD — it uploads your images to your repository and deploys them to any environments you need. However, one of the topmost requests we’ve been getting from our users so far is a way to integrate Altostra with their existing CI/CD infrastructure. Their main culprit was the need to manually authenticate with Altostra’s services.

With the API Keys feature, you can use an API key that frees you from the need to periodically authenticate with Altostra’s services — just add your API key to your CI/CD workflow, and you’re free to automatically deploy, push, sync, and invalidate while the API key handles the authentication.

In this post we’ll learn how to add a simple GitHub actions CI/CD flow to a basic Altostra API service project.

You can read more about the basic API project here, and read more about GitHub Actions here.

Using Altostra API Key with GitHub Actions

Getting the Altostra API Key

First of all, we’ll need to get an API key from Altostra.

Go to the Account Settings page in the Altostra Web Console

1. Click “Create Token”
2. Give your token a meaningful name so you’ll recognize it later
3. Keep your token somewhere safe — this is the last time you’ll see this token!

#altostra #cicd #github-actions #aws-lambda #cicd-pipeline #github