You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When tk8 is run in a directory which does not have config.yaml, it tries to auto generate it by saying:
No default config was provided. Generating one for you.
The auto-generated config.yaml is only usable for aws provisioner and not for others.
To Reproduce
Steps to reproduce the behavior:
Download tk8 binary in empty folder.
Setup cattle-aws cluster without config.yaml: tk8 cluster install cattle-aws
Expected behavior
We have two options in this case:
Instead of auto-generating config.yaml, we should tell the user to create the config.yaml before running the command since we cannot generate multiple configs for multiple provisioners.
Implement the code for mapping between different config.yaml's for different provisioners.
The text was updated successfully, but these errors were encountered:
ishantanu
changed the title
Remove auto-generation of config.yaml in empty directory
Remove/Modify auto-generation of config.yaml in empty directory
Aug 27, 2019
Describe the bug
When tk8 is run in a directory which does not have
config.yaml
, it tries to auto generate it by saying:The auto-generated
config.yaml
is only usable for aws provisioner and not for others.To Reproduce
Steps to reproduce the behavior:
tk8
binary in empty folder.config.yaml
:tk8 cluster install cattle-aws
Expected behavior
We have two options in this case:
Instead of auto-generating
config.yaml
, we should tell the user to create theconfig.yaml
before running the command since we cannot generate multiple configs for multiple provisioners.Implement the code for mapping between different
config.yaml
's for different provisioners.The text was updated successfully, but these errors were encountered: