When deploying multiple jobs using the `Databricks.yml` file via the asset bundle, the process either overwrites the same job or renames it, instead of creating separate, distinct jobs.
If I'm not mistaken, this will only work when we initialize the Databricks asset bundle. What I need is a solution that applies conditions while validating or deploying the bundle.
@filipniziolThank you for your valuable feedback. I believe the second approach aligns well with my requirements. I will implement a rollback mechanism in the target environment. Currently, I am performing all these tasks in the development environme...
I was expecting the same behavior, and I have already tried the scenario you mentioned. I believe it's due to the asset bundle, and that's acceptable.I'm trying to run integration tests when a pull request is created. The goal is to run the entire jo...
My issue is when I update a job with a different name, it's only overriding the existing job instead of creating a new one using asset bundles.Example:Step 1:This is my YAML file, and when I deploy it using asset bundles, it creates a job:bundle:
n...
