acoustic-carpenter-78188
09/25/2023, 12:06 AM--config cli flag is not respected by flytectl config init. Instead, this config always writes to ~/.flyte/config.yaml. The presence of this global flag and yet it being ignored is confusing.
(Relatedly, could flytectl suppress describing global flags that are meaningless to a specific subcommand in its help output?)
Provide a possible output or UX example
flytectl config init --config my_config.yaml
creates a file my_config.yaml in current directory.
This feature can help make the flytectl config init command more generally useful in scenarios where users may wish to store more than one config and reference appropriate configs in subsequent commands. It also happens that flytectl config init requires user input if the default path already exists and this could be problematic in CI workflows.
Are you sure this issue hasn't been raised already?
☑︎ Yes
Have you read the Code of Conduct?
☑︎ Yes
flyteorg/flyteacoustic-carpenter-78188
09/25/2023, 12:06 AM