Adds support for .env file for use with rover dev #2646
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
.env
support forrover dev
command.env
file if presentAPOLLO_GRAPH_REF
and/orAPOLLO_KEY
are supplied inline with the command those values override what is defined in.env
Manual Testing
Scenario 1: Using
.env
file containing validAPOLLO_KEY
andAPOLLO_GRAPH_REF
rover config whoami
to ensure we are using the correct API keyrover dev
with the.env
filerover config whoami
has not changedScenario 2: Using
.env
file containing invalidAPOLLO_KEY
and validAPOLLO_GRAPH_REF
rover config whoami
to ensure we are using the correct API keyrover dev
with the.env
file containing an invalidAPOLLO_KEY
rover config whoami
has not changedScenario 3: Using
.env
file containing validAPOLLO_KEY
and invalidAPOLLO_GRAPH_REF
rover config whoami
to ensure we are using the correct API keyrover dev
with the.env
file containing an invalidAPOLLO_GRAPH_REF
rover config whoami
has not changedScenario 4: Using an empty
.env
filerover config whoami
to ensure we are using the correct API keyrover dev
with empty.env
filerover config whoami
has not changedScenario 5: Supplying
APOLLO_GRAPH_REF
andAPOLLO_KEY
inline with the command and no.env
filerover config whoami
to ensure we are using the correct API keyrover dev
with variablesrover config whoami
has not changedScenario 6: Supplying
APOLLO_GRAPH_REF
andAPOLLO_KEY
inline with the command and.env
file containing an invalidAPOLLO_KEY
rover config whoami
to ensure we are using the correct API keyrover dev
rover config whoami
has not changedScenario 7: Supplying
APOLLO_GRAPH_REF
andAPOLLO_KEY
inline with the command and.env
file containing an invalidAPOLLO_GRAPH_REF
rover config whoami
to ensure we are using the correct API keyrover dev
rover config whoami
has not changedScenario 8: Supplying
APOLLO_KEY
inline with the command and.env
file containing an invalidAPOLLO_GRAPH_REF
rover config whoami
to ensure we are using the correct API keyrover dev
rover config whoami
has not changed