<#128 init_from_config looks for .flyte/config.yam...
# flyte-github
a
#128 init_from_config looks for .flyte/config.yaml files from cwd to home Pull request opened by cosmicBboy As a user, I don't want to always think about config file paths. Often times I just want to make a single config for my repo, and be guaranteed that my flyte scripts use that config. If I need to override it, I can create a config in the current working directory of where I'm running the example from. This PR makes the following changes: 1.
flyte create config
creates a config file in
./.flyte/config.yaml
by default 2. The
flyte get config
and
flyte.init_from_config
behavior is the same, for the most part, but adds the following logic: instead of looking at
./flyte/config.yaml
first, it will look for a
.flyte
directory in the current directory, then iteratively look at:
.
,
..
, etc..., until it reaches the home directory
~
. flyteorg/flyte-sdk