You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, we can import users and teams with their respective (team) authorizations. However, we cannot import teams' agents (see #692). This is because agents' authorizations must be linked to the corresponding teams' authorizations. This is usually done by the TeamService (see the documentation to learn about the implementation).
Now we want to link the user's authorization to the team's authorization (because they represent the same authorization).
We could simply add an id to the teamAuthorization object, and add a reference to this object in the user's authorization object. But both objects could be out of sync, which wouldn't be good either.
We also could simplify the authorization object with just the reference to the teamAuthorization object. But as teams are imported after users, that wouldn't work either because the reference would be null.
Solution
We should just not include "team authorizations" inside of the users' authorizations.
When we import teams, the DataImporter service should add the authorizations to the agents itself.
The text was updated successfully, but these errors were encountered:
Problem
Today, we can import users and teams with their respective (team) authorizations. However, we cannot import teams' agents (see #692). This is because agents' authorizations must be linked to the corresponding teams' authorizations. This is usually done by the
TeamService
(see the documentation to learn about the implementation).Taking an hypothetical example.
roles.json
users.json
teams.json
Now we want to link the user's authorization to the team's authorization (because they represent the same authorization).
We could simply add an id to the
teamAuthorization
object, and add a reference to this object in the user'sauthorization
object. But both objects could be out of sync, which wouldn't be good either.We also could simplify the
authorization
object with just the reference to theteamAuthorization
object. But as teams are imported after users, that wouldn't work either because the reference would be null.Solution
We should just not include "team authorizations" inside of the users' authorizations.
When we import teams, the DataImporter service should add the authorizations to the agents itself.
The text was updated successfully, but these errors were encountered: