New action: Generate integration variables

We continue to deliver quality-of-DevOps-life improvements with a new action that lets you use 3rd party integration data in pipeline actions that are not integration-specific, such as builds, VMs, and CLIs.

You will find the feature in the Setup section. The actions here let you fine-tune your pipelines to match the nuances of your company's workflow:

How it works

The new action generates variables for the selected type of integration and makes them available for the time of the pipeline execution. At the moment, the following integrations are supported:

• AWS: AWS_SESSION_TOKEN, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY
• DOCKER_HUB: DOCKER_USER, DOCKER_PASS
• GITHUB_API: GIT_HUB_USERNAME, GIT_HUB_TOKEN

Use case

Let's assume you have a pipeline with an action that requires a Docker image hosted on the Amazon ECR. The action is Docker VM, a Linux machine with Docker installed. Generating the variables will let you connect to the registry, pull the image to that VM and run commands:

All you need to do is add this action at the beginning of the pipeline – Buddy will automatically fetch the authorization data in subsequent actions: