Closed astrojuanlu closed 1 year ago
Usage: kedro new [OPTIONS]
Create a new kedro project.
Options:
-v, --verbose See extensive logging and error stack traces.
-c, --config PATH Non-interactive mode, using a configuration yaml file.
This file must supply the keys required by the
template's prompts.yml. When not using a starter, these
are `project_name`, `repo_name` and `python_package`.
-s, --starter TEXT Specify the starter template to use when creating the
project. This can be the path to a local directory, a
URL to a remote VCS repository supported by
`cookiecutter` or one of the aliases listed in ``kedro
starter list``.
--checkout TEXT An optional tag, branch or commit to checkout in the
starter repository.
--directory TEXT An optional directory inside the repository where the
starter resides.
-h, --help Show this message and exit.
You can either commit this to a testing branch and use --checkout
or clone the repository locally and use the --directory
flag for testing.
This approach has some drawbacks and goes against the current philosophy of this starter as discussed in gh-115, closing this PR for now.
Motivation and Context
To close gh-115.
How has this been tested?
I haven't tested it, copy-pasted the
pyproject.toml
from spaceflights. Is there a way to specify a custom path or repo for akedro new
starter? Otherwise ideas for testing this are welcome.Checklist