https://community.databricks.com/t5/get-started-discussions/databricks-bundles-good-practice-for-multiprocessing-envs/m-p/67635#M7177 <P><SPAN>I'm seeking advice regarding Databricks bundles. In my scenario, I have multiple production environments where I aim to execute the same DLT. To simplify, let's assume the DLT reads data from 'eventhub-region-name,' with this being the only differing factor. Therefore, I can parameterize a variable and utilize it as a configuration parameter in the DLT definition.</SPAN></P><P>However, I'm unsure about the best practice for targeting. Both environments are production, and I prefer to keep the code simple. Should I define something like 'prod-1' and 'prod-2' as targets, or is there a better approach?</P> Tue, 30 Apr 2024 02:17:26 GMT mderela 2024-04-30T02:17:26Z https://community.databricks.com/t5/get-started-discussions/databricks-bundles-good-practice-for-multiprocessing-envs/m-p/67635#M7177 <P><SPAN>I'm seeking advice regarding Databricks bundles. In my scenario, I have multiple production environments where I aim to execute the same DLT. To simplify, let's assume the DLT reads data from 'eventhub-region-name,' with this being the only differing factor. Therefore, I can parameterize a variable and utilize it as a configuration parameter in the DLT definition.</SPAN></P><P>However, I'm unsure about the best practice for targeting. Both environments are production, and I prefer to keep the code simple. Should I define something like 'prod-1' and 'prod-2' as targets, or is there a better approach?</P> Tue, 30 Apr 2024 02:17:26 GMT https://community.databricks.com/t5/get-started-discussions/databricks-bundles-good-practice-for-multiprocessing-envs/m-p/67635#M7177 mderela 2024-04-30T02:17:26Z