-
Notifications
You must be signed in to change notification settings - Fork 906
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
Do not fail if conf/local
is not present
#2593
Comments
Double check with @idanov why this is so strictly enforced. |
+1, would love to see this change. |
I talked to @idanov about this and he said the main reason this error has been put in is to make users aware that config is layered: as in it's not just the one file, but you can have different environments to override whatever is in base. If the I see the benefit in keeping to error to create awareness. Has anyone seen complaints from users about this behaviour? |
That makes sense. I personally haven't seen any complaints, because I assume most people run For anyone trying to manually craft a Kedro project in an existing directory (without doing At the minimum, if we are to keep the error message (which I'm still not sold on), I think we should conceal the traceback of this one #2401 |
We have now alternative ways to use Kedro as a library without submitting to all the assumptions of Kedro framework, so given that there was support to keep the error message and that we have already agreed to do #2971, I'm closing this issue as not planned. |
...but let's try to make the traceback more manageable #2401 |
FTR, I'm personally struggling again with this on Databricks... |
Description
As per title.
Context
On a perfectly functioning project with an empty
conf/local
, if the directory is removed,kedro run
will fail:Just recreating the directory
mkdir conf/local
makes everything work again.When converting an existing project to a Kedro one (gh-410), this creates unnecessary toil, because it forces the user to create some directories and files even though initially they are empty or unused.
Notice that this doesn't mean removing
conf/local
from the project templates - just being more permissive if users are not starting withkedro new
.Possible Implementation
Issuing a warning if the directory is not found, and proceeding as normal.
If the environment is manually set, the current error could be kept (but not the traceback, see gh-2401):
Possible Alternatives
Alternatively, we could keep the error for all cases, but conceal the traceback as argued in gh-2401.
The text was updated successfully, but these errors were encountered: