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

Only create a new environment when --configure-env flag is passed in #1412

Closed
vishalbollu opened this issue Sep 30, 2020 · 0 comments · Fixed by #1533
Closed

Only create a new environment when --configure-env flag is passed in #1412

vishalbollu opened this issue Sep 30, 2020 · 0 comments · Fixed by #1533
Assignees
Labels
bug Something isn't working
Milestone

Comments

@vishalbollu
Copy link
Contributor

vishalbollu commented Sep 30, 2020

Version

<= 0.21.0

Description

cortex cluster info automatically creates or overwrites the aws environment if the --env isn't specified. Rename --env to --configure-env and only create or update the environment if it is specified.

Update documentation that specified the use of cortex cluster info for getting/updating environments.

@vishalbollu vishalbollu added the bug Something isn't working label Sep 30, 2020
@vishalbollu vishalbollu changed the title Create a new environment when --env flag is passed in Only create a new environment when --env flag is passed in Oct 1, 2020
@vishalbollu vishalbollu changed the title Only create a new environment when --env flag is passed in Only create a new environment when --configure-env flag is passed in Oct 27, 2020
@deliahu deliahu self-assigned this Oct 31, 2020
@deliahu deliahu added the v0.22 label Oct 31, 2020
@deliahu deliahu added this to the v0.23 milestone Nov 26, 2020
@deliahu deliahu added v0.22 and removed v0.23 labels Nov 26, 2020
@deliahu deliahu modified the milestones: v0.23, v0.22 Nov 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants