-
Notifications
You must be signed in to change notification settings - Fork 893
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
Add a deprecation notice to signal the archiving of starters + new project creation flow #3114
Comments
Bringing here some concerns that @datajoely raised on #3173:
We would be archiving the old starters and not removing them, so as far as I understand Kedro 0.18 with the old starters will keep working for the time being. Are we missing something?
Again, as far as I understand, the plan is to make the
(and by omission, when all flags are chosen, no interactive flow will appear) More broadly, this breaking change will require downstream projects to adapt to the new way, but we think the end result is going to be superior to what we have nowadays. Please let us know your thoughts on this thread. |
So if you look at how an alloy app is configured here, Alloy retrieves the cookiecutter template directly https://brix.quantumblack.com/products/alloy/docs/01_intro/key_concepts/#app If you drop this from 0.19.x there will be barrier for Verticals adopting the latest version of Kedro |
Description
In Kedro
0.19.0
we're removing some of the starters and introducing a completely new project creation flow. We should add warnings/info to our users ahead of this so they know this flow will change.Context
Possible Implementation
kedro new
flow that explains the changes that are coming.kedro starter list
and add (deprecated/archived) to the starters that will be archived in Archive "non-unique" starters #3113The text was updated successfully, but these errors were encountered: