# Simplify switching between developer environments

**URL:** <https://community.holistics.io/t/simplify-switching-between-developer-environments/1524>\
**Category:** Feature Suggestions\
**Created:** [May 26, 2023, 5:18pm UTC](https://community.holistics.io/t/simplify-switching-between-developer-environments/1524 "2023-05-26T17:18:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![SterlingParamoreMSE](https://community.holistics.io/user_avatar/community.holistics.io/sterlingparamoremse/32/689_2.png) [@SterlingParamoreMSE](https://community.holistics.io/u/SterlingParamoreMSE)\
**Post date:** [May 26, 2023, 5:18pm UTC](https://community.holistics.io/t/simplify-switching-between-developer-environments/1524/1 "2023-05-26T17:18:58Z")

</div>

We have a team of dbt developers. We use Snowflake. Each developer can build dbt models in their own isolated Snowflake database. When we want to test out model changes in Holistics, it’s a bit of a pain. The procedure is:

1. Set up a new data connection that is specific to the developer and points to their developer database.
2. Write AML code, but set the `data_source_name` parameter to the developer connection.
3. Test the new model and go through the code review process.
4. Change the `data_source_name` parameter back to the production connection.
5. Merge the changes.

In my ideal world I be able to set up one developer connection that could be parameterized during AML development (e.g., change the database name or the warehouse). Then I could also choose to develop AML against my parameterized development data connection. This would reduce the number of data connections I have to set up and maintain, and wouldn’t require devs to remember to switch back-and-forth between changing the data connection during development.

---

<div class="post-metadata">

**Author:** ![Abdel](https://community.holistics.io/user_avatar/community.holistics.io/abdel/32/299_2.png) [@Abdel](https://community.holistics.io/u/Abdel)\
**Post date:** [June 5, 2023, 3:05pm UTC](https://community.holistics.io/t/simplify-switching-between-developer-environments/1524/2 "2023-06-05T15:05:37Z")

</div>

This is a long discussed problem, since I joined the Holistics community 2 years ago. I didnt see any significant progress on that

---

<div class="post-metadata">

**Author:** ![Khai\_To](https://community.holistics.io/user_avatar/community.holistics.io/khai_to/32/128_2.png) [@Khai\_To](https://community.holistics.io/u/Khai_To)\
**Post date:** [October 28, 2024, 3:26am UTC](https://community.holistics.io/t/simplify-switching-between-developer-environments/1524/3 "2024-10-28T03:26:07Z")

</div>

Hi @SterlingParamoreMSE and @Abdel,

We’re gathering beta testers for our new Dynamic Data Sources, and think you’d be a great fit!  
Check out the details in our [Community Post](https://community2.holistics.io/t/upcoming-introducing-dynamic-data-sources/2140) and submit [a request](https://form.jotform.com/230511857392457/prefill/67039d093162304208b4f2c22b48) if you’re interested.

Let me know if you have any questions!