Re-add support for dbt init <project_name>

[jtcohen6]

Folks are used to being able to pass project name as a first positional argument to the dbt init subcommand. The new approach (new for v1!) is much more fun + interactive, but for muscle memory's sake, let's see if we can't find a way to keep supporting dbt init my_new_project, too.

If passed, I think this argument should be used as the implicit answer for "What is the desired project name?" We should set project_name accordingly here, and skip the prompt.

Related ask that we should foresee:

• Ability to skip profile setup entirely, and just create scaffolding for a new project (--skip-profile-setup?). This could be used by tools which manage connection setup themselves, such as dbt Cloud
• Ability to create project scaffolding in the current working directory, rather than always creating a new subfolder ([Feature] dbt init with target directory #4141)

[kadero]

Hello @jtcohen6 👋,

Indeed, it could be great to keep supporting dbt init my_new_project for the v1 🙂.

Ability to skip profile setup entirely, and just create scaffolding for a new project (--skip-profile-setup?). This could be used by tools which manage connection setup themselves, such as dbt Cloud

I agree too, this feature would be use full 🙂.

Happy to can work on it if it's ok for you? 🙂
Thanks 🙏

[jtcohen6]

By all means!

[b-per]

Hi @kadero, have you worked on this one already? If not, I am happy to raise a PR for it.

[kadero]

Hi @kadero, have you worked on this one already? If not, I am happy to raise a PR for it.

Hello @b-per,
Thanks for your message 🙂 .

Yes I began to work on it. I didn't find the time to finish the job (fix integration tests) and open a PR. I'm going to open a PR ASAP.

Thanks 🙏