Replies: 1 comment
-
hi @JonasDev1 , you can implement this API call and programmatically substitute the user by using the custom functions. e.g. you add a function to retrieve the current user: # .dbx/_custom_jinja_functions.py
def retrieve_current_user() -> str:
... And then use it inside your environments:
default:
workflows:
- name: "example-workflow"
access_control_list:
- service_principal_name: {{ custom.retrieve_current_user() }}
permission_level: "IS_OWNER" |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey there,
due to the fact that normal users can't change the workflow owner, we always use the deployment user as the workflow owner. Currently we have multiple deployment users(one for each permission group) and always have to set the owner name manually.
I saw that there is a current user API endpoint. With this it's possible to set the owner automatically. I would prefer to use a named property.
With the new reference-based approach, it would look like this:
What are your thoughts?
Beta Was this translation helpful? Give feedback.
All reactions