Ashok Singamaneni
Ashok Singamaneni
Disccussed with @pariksheet and @stikkireddy - We will be going with BRICKFLOW_PROJECT_PARAMS and use cli to pass the params. The parameters would be available through ctx and a helper function.
We also need to probably need to hard set the schedule as None if the env is local.
For local: we will default it to None, but will give an option to override and schedule it For dev, qa & prod: Folks should be able to decide the...
I agree, makes sense!
We want to enable this option only for: --env local. If there are 3 workflows already existing in the Databricks remote, then if we use -w and deploy a new...
We would not want to deploy single workflows via CI/CD as that would require us to maintain and manage the state other than what DAB provides us. Want this option...
@lbakshi Would to be able to work on this issue and raise a pr?
The feature is already available. We need to add this to the documentation!
@amaldevk88 Looks like the lint checks failed, can you please correct and run `make cov` in your local to validate everything is right. Thanks!
@amaldevk88 can you please fix the unittests.