-
Notifications
You must be signed in to change notification settings - Fork 908
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
[Spike] - Add a feature to add new tools to the existing kedro project #3689
Comments
+1 would love this |
Hi @gopiande, thanks for this feature request! We discussed this feature when introducing the new tools workflow on project creation. But at the time decided to not implement too many things at once, in case nobody uses it. It's great to see this is something our users would be interested in. I will add this to our backlog 😄 |
It's unclear how to add a new tool. Since the current approach is removing tools from a project template. Some investigation is needed to get some proposals or exploring other approach. |
https://docs.kedro.org/en/stable/starters/create_a_starter.html#extend-starter-aliases Alternatively, the old approach of creating a new project template would still work. However, you won't have the option to choose a specific tool during the project creation. |
A user was asking about this today (Linen archive is not up to date, so sharing the Slack link instead: https://kedro-org.slack.com/archives/C03RKP2LW64/p1725320318538009 |
Description
Currently, I can add the tools only when creating a new Kedro project. But, sometimes we might want to add more tools later and currently, there is no option to add them later using a command.
For example, I created a new Kedro project with a basic lint tool initially but after some time I realized that I needed to add data/docs directories, then it would be a good thing to have a command to automatically add those directories. Currently, I have to do it manually or create a new project with those tools and move the existing ones to the new one.
The text was updated successfully, but these errors were encountered: