OpenMetadata is a unified metadata platform for data discovery, data observability, and data governance powered by a central metadata repository, in-depth column level lineage, and seamless team collaboration.
Is your feature request related to a problem? Please describe.
Currently creation of bots allows granting them one of available Roles. These roles, however, grant quite broad set of permissions to bots and cannot be scoped easily to single schema etc. There is no easy way to create a bot that could be used on behalf of OpenMetadata Team members.
Exemplary use case for this feature would be as such:
each schema in OpenMetadata is owned by different OpenMetadata Team
let's assume there is project x in the organization, this project has corresponding Team in OM and is assigned as owner of schema xdb in OpenMetadata
each member of project x can, using personal credentials or UI, edit metadata of xdb schema (default behaviour of RBAC in OM)
project x has set of metadata they want to update automatically + run profiling jobs automatically using OM SDK (for example - via scheduler airflow pipelines executed outside OpenMetadata Airflow instance)
there is project-x-bot which has same permissions as any other member of project x but is treated like NPA (non personal account)
members of projectx use project-x-bot account with it's JWT Token credentials to update metadata using OpenMetadata SDK. This bot can only edit entitites for which project x is an owner
Describe the solution you'd like
This feature request is about adding a possibility to treat bot as Team member and thus - such bot would have permission scoped to this Teams permissions.
Is your feature request related to a problem? Please describe.
Currently creation of bots allows granting them one of available Roles. These roles, however, grant quite broad set of permissions to bots and cannot be scoped easily to single schema etc. There is no easy way to create a bot that could be used on behalf of OpenMetadata
Team
members.Exemplary use case for this feature would be as such:
Team
x
in the organization, this project has correspondingTeam
in OM and is assigned as owner of schemaxdb
in OpenMetadatax
can, using personal credentials or UI, edit metadata ofxdb
schema (default behaviour of RBAC in OM)x
has set of metadata they want to update automatically + run profiling jobs automatically using OM SDK (for example - via scheduler airflow pipelines executed outside OpenMetadata Airflow instance)project-x-bot
which has same permissions as any other member of projectx
but is treated like NPA (non personal account)x
useproject-x-bot
account with it's JWT Token credentials to update metadata using OpenMetadata SDK. This bot can only edit entitites for which projectx
is an ownerDescribe the solution you'd like
This feature request is about adding a possibility to treat bot as Team member and thus - such bot would have permission scoped to this Teams permissions.
Describe alternatives you've considered n/a
Additional context n/a