Skip to content

DO-1743: Add EXTRA_VARS and EXTRA_SECRETS #170

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AdamJHall merged 2 commits into from
Jul 6, 2026
+24 −0
Merged

DO-1743: Add EXTRA_VARS and EXTRA_SECRETS #170

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8495d40
Allow the passthrough of EXTRA_VARS and EXTRA_SECRETS to the GITHUB_E…
AdamJHall Jul 6, 2026
fbf0e32
Add note about the format of EXTRA_VARS / SECRETS
AdamJHall Jul 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions .github/workflows/aws-cdk.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -226,6 +226,22 @@ jobs:
;;
esac

- name: Export extra environment variables
env:
EXTRA_VARS: ${{ vars.EXTRA_VARS }}
EXTRA_SECRETS: ${{ secrets.EXTRA_SECRETS }}
run: |
if [ -n "$EXTRA_VARS" ]; then
while IFS= read -r line; do
[ -n "$line" ] && echo "$line" | tr -d '\r' >> "$GITHUB_ENV"
done <<< "$EXTRA_VARS"
fi
if [ -n "$EXTRA_SECRETS" ]; then
while IFS= read -r line; do
[ -n "$line" ] && echo "$line" | tr -d '\r' >> "$GITHUB_ENV"
done <<< "$EXTRA_SECRETS"
fi

- name: Set CDK commands
id: parse-cdk-config
env:
Expand Down
8 changes: 8 additions & 0 deletions docs/aws-cdk.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,14 @@ These should be configured in your GitHub Environment (or at the repository leve

> **Authentication:** Configure either static credentials (`AWS_ACCESS_KEY_ID` + `AWS_SECRET_ACCESS_KEY`) **or** OIDC (`AWS_ROLE_ARN`). The workflow auto-detects which method to use.

**Extras** — optional:

| Name | Type | Description |
|------|------|-------------|
| `EXTRA_VARS` | Variable | Additional non-secret environment variables to inject into the deploy step |
Comment thread
AdamJHall marked this conversation as resolved.
| `EXTRA_SECRETS` | Secret | Additional secret environment variables to inject into the deploy step |

Both extra fields accept multiline `KEY=VALUE` pairs — one per line. Use these for runtime configuration that varies per project, such as feature flags.

#### **Outputs**
| Name | Description |
Expand Down