In Github Actions, by default, data is not inherently persistent or available to the whole pipeline. Every step has is its own process, every job has its own runner. By default, whatever data emerges in a job, ends with it.

How do we pass data from one process to the other, or save it for the next process?

A short sweet answer:

For a completer answer: read on.
All the workflow examples in this article can be found as files here, along with a copy of the respective redacted logs.

In this article I’ll use Step Functions as a case study, but you can do it with whatever resources you want.

What we’re going to do​

The following JSON will become dynamic. We’ll replace static values with:

1. A variable
2. A dynamic list
3. One or more dynamic objects

Have you ever came across this Terraform error — when you intentionally want your ternary to output different types?

The true and false result expressions must have consistent types

To bypass this Terraform limitation, check the tip below. I'll follow it with two examples to clarify the usage:

attribute = [
    <desired output if true>, 
    <desired output if false>
    ][<condition> ? 0 : 1]

This tutorial includes guidance for three different scenarios in your GitHub administration:

1. when your repo is in your personal account;
2. when your app is under a GitHub Org and admins grant you the permissions you need; and
3. when your repo is under a GitHub Org and admins do NOT grant you the permissions you need.

Pre-requisites: Relevant access and permissions for CodeCommit and Amplify. You also need a working GitHub account.