โ02-20-2023 12:49 PM
I know that the run_as user generally defaults to the creator_user, but I would like to find the defined run_as user for each of our jobs. Unfortunately, I'm unable to locate that field in the api.
โ02-22-2023 04:49 AM
>> Thanks for reaching out to us. In order to update run_as_user in API 2.1, you need to change the job owner to the respective user defined in the access_control_list.
Thank you. Unfortunately, I am not trying to update the run_as_user, but I am trying to retrieve it.
Upon closer reading of the yaml for Jobs API 2.1, it looks like run_as_user for a job is available via 'get' (for an individual job), but is not returned as part of 'list'. So it appears the confusion is mine.
I would suggest that in the future, perhaps ownership/privilege information would be valuable as part of job list retrieval.
Thanks for the help!
โ02-21-2023 07:55 AM
Hi @Keller, Michaelโ,
Thanks for reaching out to us. In order to update run_as_user in API 2.1, you need to change the job owner to the respective user defined in the access_control_list.
โ02-22-2023 04:49 AM
>> Thanks for reaching out to us. In order to update run_as_user in API 2.1, you need to change the job owner to the respective user defined in the access_control_list.
Thank you. Unfortunately, I am not trying to update the run_as_user, but I am trying to retrieve it.
Upon closer reading of the yaml for Jobs API 2.1, it looks like run_as_user for a job is available via 'get' (for an individual job), but is not returned as part of 'list'. So it appears the confusion is mine.
I would suggest that in the future, perhaps ownership/privilege information would be valuable as part of job list retrieval.
Thanks for the help!
โ02-21-2023 10:48 PM
Hi @Keller, Michaelโ
Hope all is well! Just wanted to check in if you were able to resolve your issue and would you be happy to share the solution or mark an answer as best? Else please let us know if you need more help.
We'd love to hear from you.
Thanks!
โ03-01-2023 05:41 AM
thanks, I picked my own reply as the 'right' answer. i'd still recommend that the jobs api perhaps incorporate run-as-user in the 'list' method, rather than only in job details.
Join a Regional User Group to connect with local Databricks users. Events will be happening in your city, and you wonโt want to miss the chance to attend and share knowledge.
If there isnโt a group near you, start one and help create a community that brings people together.
Request a New Group