refactor(bundle): use named_parameters rather than parameters #96
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR replaces use of
See https://docs.databricks.com/api/workspace/jobs/createparameters
bynamed_parameters
in the task definition.The purpose of this change is to benefit of making job parameters available as task parameters:
https://docs.databricks.com/en/jobs/task-parameters.htmlUsing job parameters as task parameters would give the ability to define a
params
argument at the databricks job level that would be passed from the databricks job to the databricks tasks and so it would give the ability to use the kedroruntime_params:
resolver.