[CT-2873] [Feature] dbt init should create project in current dir (.) instead of creating a new dir

[dataders]

Is this your first time submitting a feature request?

• I have read the expectations for open source contributors
• I have searched the existing issues, and I could not find an existing issue for this feature
• I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature

TL;DR: I want dbt init to behave like git init and by default work within the current directory rather than make a new directory.

from the git init (docs page):

If the $GIT_DIR environment variable is set then it specifies a path to use instead of ./.git for the base of the repository.

Describe alternatives you've considered

• a command-line flag to override this directory-creation step?
• guidance that users should follow explicitly these steps in order:
  • dbt init
  • cd my_new_dbt_proj_dir
  • git init

Who will this benefit?

those who need to quickly make standalone project examples and sync them to GitHub

Are you interested in contributing this feature?

yes

Anything else?

I noticed that the dbt init docs are missing information that's provided in the CLI via dbt init -h

[dbeatty10]

Agreed -- I always expected dbt init to use the current working directory as you described with git init.

But since this is such long-standing behavior, I think we'd need to use one of the alternatives you mentioned instead:

• a command-line flag to override this directory-creation step?
• guidance that users should follow explicitly these steps in order:
  • dbt init
  • cd my_new_dbt_proj_dir
  • git init

Maybe a global config option named INIT_DIR (so that it can get included in the global profiles.yml) along with DBT_INIT_DIR environment variable and --init-dir CLI flag?

I noticed that the dbt init docs are missing information that's provided in the CLI via dbt init -h

Would you mind opening an issue (or a PR) in docs.getdbt.com?

[github-actions]

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.

[github-actions]

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.

[github-actions]

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.

[jtcohen6]

@dataders @dbeatty10 I agree; I think we should modify this behavior. This issue has come up several times over the years:

• dbt init should be able to create a project in the current directory #1121 (TC in 2018!)
• [Feature] dbt init with target directory #4141
• [CT-3363] [Feature] interactive dbt init flow's instructions don't results in a successful dbt debug, because you need to enter the new subdirectory #9041

Unfortunately, it doesn't really make sense to set as a flag / global config (which are moving to dbt_project.yml: #9183), because by definition the dbt_project.yml file doesn't exist yet!

So I think we just need to change it for good, and document that achieving the previous behavior will require running:

$ mkdir <projectname>
$ cd <projectname>
$ dbt init