Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2025 02:48 PM
Hello,
I would like to revisit this topic as I now have a clearer understanding of my needs and the issue at hand.
Let’s assume we have only one active Databricks workspace, which currently serves as both development and production. This dual role adds complexity to managing deployments effectively.
My question is:
- How can we ensure that if someone attempts to deploy the databricks.yml file in this same workspace, it does not recreate an existing workflow?
- Specifically, how can we avoid creating duplicate workflows, even if the deployment is performed by a different user or creator?
Since we are working with a single workspace (i.e., one target acting as both dev and prod), it’s crucial to prevent redundancy and maintain consistency.
Thank you for your assistance!