# \[DBT x Cosmos X GCP\] So far we must duplicate the dbt project in two different locations

**URL:** <https://discourse.getdbt.com/t/dbt-x-cosmos-x-gcp-so-far-we-must-duplicate-the-dbt-project-in-two-different-locations/19940>\
**Category:** In-Depth Discussions\
**Tags:** gcp-cloud-composer, dbt-core\
**Created:** [July 25, 2025, 3:52pm UTC](https://discourse.getdbt.com/t/dbt-x-cosmos-x-gcp-so-far-we-must-duplicate-the-dbt-project-in-two-different-locations/19940 "2025-07-25T15:52:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jpaublant](https://avatars.discourse-cdn.com/v4/letter/j/d6d6ee/32.png) [@jpaublant](https://discourse.getdbt.com/u/jpaublant)\
**Post date:** [July 25, 2025, 3:52pm UTC](https://discourse.getdbt.com/t/dbt-x-cosmos-x-gcp-so-far-we-must-duplicate-the-dbt-project-in-two-different-locations/19940/1 "2025-07-25T15:52:06Z")

</div>

Hello,

I’m in the process of deploying a dbt pipeline on GCP using the Cosmos extension. While I’ve successfully set it up, there’s a significant drawback: we have to upload the dbt project on GCP at two specific locations.

It appears that Cosmos doesn’t offer the capability to scan the project if it resides in a different bucket than the one used for Composer.

Does anyone have a workaround for this?

Thanks