Update cloud-cli-installation.md

[jeremyyeo]

What are you changing in this pull request and why?

Making users aware of limitation https://dbt-labs.slack.com/archives/C019QLR6EJE/p1721233164421329

Checklist

• I have reviewed the Content style guide so my content adheres to these guidelines.
• The topic I'm writing about is for specific dbt version(s) and I have versioned it according to the version a whole page and/or version a block of content guidelines.
• I have added checklist item(s) to this list for anything anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."
• The content in this PR requires a dbt release note, so I added one to the release notes page.

---

🚀 Deployment available! Here are the direct links to the updated files:

• https://docs-getdbt-com-git-jeremyyeo-patch-3-dbt-labs.vercel.app/docs/cloud/cloud-cli-installation
• https://docs-getdbt-com-git-jeremyyeo-patch-3-dbt-labs.vercel.app/docs/cloud/configure-cloud-cli

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs-getdbt-com	✅ Ready (Inspect)	Visit Preview	Feb 20, 2025 0:11am

[mirnawong1]

hey @jeremyyeo ! thanks for opening this up. how does the below sound so there's more context:

The dbt Cloud CLI doesn't currently support relative paths in the packages.yml file. This mostly applies to organizations that use a monorepo structure.

For example, trying to reference the shared_macros directory from your packages.yml file like this won't work:

# repository_root/my_dbt_project_in_a_subdirectory/packages.yml

packages:
  - local: ../shared_macros

In this example, ../shared_macros is a relative path that tells dbt to look for:

• .. — Go one directory up (to repository_root).
• /shared_macros — Find the shared_macros folder in the root directory.

To work around this limitation:

• Use the dbt Cloud IDE to support relative paths for this use case.
• If using a monorepo with multiple projects as subdirectories, use private packages or the git clone method to share package across projects.
• If using monorepo with single project, store the package in the same repository as the project.

[jeremyyeo]

Did you test if private packages works with dbt Cloud CLI? Not sure at the top of my head :)

[mirnawong1]

i didn't but i was having a chat with Lucas Silbernagel about this and that's here i got it from. should i juts remove that bullet and just let users know to use the ide??

[mirnawong1]

ok @jeremyyeo , changed it to this:

The dbt Cloud CLI doesn't currently support relative paths in the packages.yml file.

For example, trying to install a local package (shared_macros directory) in your packages.yml file won't work:

# repository_root/my_dbt_project_in_a_subdirectory/packages.yml

packages:
  - local: ../shared_macros

In this example, ../shared_macros is a relative path that tells dbt to look for:

• .. — Go one directory up (to repository_root).
• /shared_macros — Find the shared_macros folder in the root directory.

To work around this limitation, use the dbt Cloud IDE, which supports relative paths for this use case.

[mirnawong1]

hey @jeremyyeo , ok how's this looking now:

[mirnawong1]

confirmed by Jeremy!