Skip to content
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.

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

fix: check for local env file and then fall back on exeinfo #6500

Merged
merged 1 commit into from Jan 28, 2021

Conversation

ammarkarachi
Copy link
Contributor

Issue #, if available:

Description of changes:
The local env file is not present when the root stack is initialized on an existing project. The envName and projectName are extracted from the exeInfo as a fall back

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@ammarkarachi ammarkarachi requested a review from a team as a code owner January 28, 2021 16:57
Copy link
Contributor

@jhockett jhockett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just one minor nit

@jhockett jhockett merged commit d2bc6d8 into aws-amplify:master Jan 28, 2021
@github-actions
Copy link

This pull request has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

src/project/amplify/.config/local-env-info.json' error raised when deploy.
2 participants