GitHub Actions: Scoping environment variables across environments without wildcards

GitHub Actions does not support wildcard scoping for environment variables, unlike GitLab CI.

It does support named environments with their own variables and secrets under Settings → Environments.

A reusable deployment workflow can build the environment name from inputs.environment and inputs.name, with an apps segment.

With 10 apps and 3 tiers, the setup creates 30 environments; tier-wide values like AWS_OIDC_IAM_ROLE_ARN, CDK_DEFAULT_ACCOUNT, and DOMAIN can stay shared.

Setting 15 variables on each of 30 environments would create 450 entries, so the article stores tier-specific config in an ENVIRONMENT_CONFIG JSON repository variable.