adamgorkaextbi opened a new issue, #45738:
URL: https://github.com/apache/airflow/issues/45738

   ### Apache Airflow Provider(s)
   
   databricks
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-databricks==7.0.0
   
   ### Apache Airflow version
   
   2.10.4
   
   ### Operating System
   
   Linux
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   official Helm Chart
   
   ### What happened
   
   DatabricksWorkflowOperator do not update ACL on workflow reset, this is done 
only during creation of workflow (Databricks API 2.0 implementation)
   one more call is needed to Databricks API 2.0
   
   ### What you think should happen instead
   
   DatabricksWorkflowOperator on  workflow reset should also update ACL in next 
api call
   
   ### How to reproduce
   
   try to modify ACL after creation of workflow
   
   ### Anything else
   
   Proposed solution:
   after this line:
   
https://github.com/apache/airflow/blob/6cde25f1ac005e217b32f19a8bf1be75bf8e7af6/providers/src/airflow/providers/databricks/operators/databricks_workflow.py#L179
   add this code:
   ```
               if "access_control_list" in job_spec.keys():
                   access_control_list = {"access_control_list": 
job_spec["access_control_list"]}
                   self.log.info(
                       "Updating ACL of Databricks workflow job %s with spec 
%s",
                       self.job_name,
                       json.dumps(access_control_list, indent=2),
                   )
                   self._hook.update_job_permission(job_id, access_control_list)
   ```
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to