aws-amplify / aws-amplify/amplify-cli

How can you define custom environment-specific variables?

Open
#1,366 22 comments 19 reactions 0 assignees View on GitHub
auth feature-request multienv p3 pending-review platform strategic
Dominant language
TypeScript
Stars
2.9k
Forks
825
Avg merge
11d 23h
Merged PRs (30d)
2

Description

** Which Category is your question related to? **
AWS Amplify cli general

** What AWS Services are you utilizing? **
N/A

** Provide additional details e.g. code snippets **
Is there a way to provide additional environment-specific variables that would be updated (e.g. in `aws-exports.js`) when using `amplify env checkout`?

For example, we manually configure an OAuth domain for each of our environments. We would want to have this as an environment-specific variable which would be available from `aws-exports.js` (or some other place) which would automatically update when we do `amplify env checkout`. (Currently `aws-exports.js` doesn't even contain the environment name, so we cannot create a manual environment map based on it.)

Contributor guide

Open the contributing guide

Research direction

Start by tracing how `amplify env checkout` updates `aws-exports.js` and where environment configuration is generated. Define how user-provided environment-specific values should be stored and exposed, then verify that checking out each environment produces the corresponding values without breaking existing exports.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, typescript
Domain
cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.