GitHub user Yicong-Huang edited a comment on the discussion: Improvement: Treat TexeraAgents as access-controlled Resources, just like other resources (workflows, datasets and computing units)
I do believe you are talking about managing metadata of agents, which is the CRUD of creating agent as a resource. There is one thing missing in the discussion, which is the access control service, the access grant of which user can manage which agent should be routed to that service. After an agent is created, the access control service should gate it as a resource: only user who has certain privilege can access the agent. Please add that part into the discussion. I agree such metadata it should be persisted. and agree with the proposal in general. Let's see the details after you revise the discussion. One more thing, which I think you partially touched upon, is how do user collaborate with agents. There are in general two ways: 1. agent act (send requests to other services) on behalf of a human user. 2. we treat agent as a real user, and human user has to grant access to a certain resource to an agent user. Then agent user can act. I think this needs further discussion. GitHub link: https://github.com/apache/texera/discussions/5302#discussioncomment-17198743 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
