-
Notifications
You must be signed in to change notification settings - Fork 384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added databricks_job
data resource
#1509
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left naming requirements in the PR. Look at the recent merged PRs that were adding data sources:
- PR name must be compliant - it goes to release notes almost unchanged. In a current shape I have to change it a bit.
- Look at recently added cluster “singular” data source.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Plus other renames required
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #1509 +/- ##
==========================================
+ Coverage 89.57% 90.04% +0.46%
==========================================
Files 135 136 +1
Lines 10825 10847 +22
==========================================
+ Hits 9697 9767 +70
+ Misses 737 690 -47
+ Partials 391 390 -1
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
consistency issues, suggested fixed whenever they're applicable
databricks_job
data resource
Example: Getting the existing cluster id of specific databricks_job by name or by id: ``` data "databricks_job" "this" { job_name = "My job" } output "cluster_id" { value = data.databricks_job.job_settings.existing_cluster_id sensitive = false } ``` Co-authored-by: Serge Smertin <259697+nfx@users.noreply.github.com>
Example: Getting the existing cluster id of specific databricks_job by name or by id: ``` data "databricks_job" "this" { job_name = "My job" } output "cluster_id" { value = data.databricks_job.job_settings.existing_cluster_id sensitive = false } ``` Co-authored-by: Serge Smertin <259697+nfx@users.noreply.github.com>
Retrieves the settings of databricks_job by name or by id. Complements the feature of the databricks_jobs data source.
Example Usage
Getting the existing cluster id of specific databricks_job by name or by id:
Attribute Reference
This data source exports the following attributes:
job_id
- the id of databricks_job if the resource was matched by name.job_name
- the job name of databricks_job if the resource was matched by id.job_settings
- the job settings of databricks_job.Related Resources
The following resources are used in the same context: