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

[FlyteCTL Feature] Sandbox and demo teardown command should better give instruction to unset env var #3689

Closed
2 tasks done
honnix opened this issue May 16, 2023 · 0 comments · Fixed by flyteorg/flytectl#403
Labels
enhancement New feature or request untriaged This issues has not yet been looked at by the Maintainers

Comments

@honnix
Copy link
Member

honnix commented May 16, 2023

Describe the feature/command for FlyteCTL

After running start command for sandbox and demo, flytectl prints the instruction to set FLYTECTL_CONFIG env var pointing to a config file made for the sandbox/demo; however the teardown command does not tell users to unset the env var. So very often, users end up with having FLYTECTL_CONFIG pointing to an invalid config file, and that makes any other flytectl commands not being executed correctly towards a production setup.

Provide a possible output or UX example

Teardown command could print out something like: please run unset FLYTECTL_CONFIG to clean up the environment variable.

Are you sure this issue hasn't been raised already?

  • Yes

Have you read the Code of Conduct?

  • Yes
@honnix honnix added enhancement New feature or request untriaged This issues has not yet been looked at by the Maintainers labels May 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request untriaged This issues has not yet been looked at by the Maintainers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant