Instance admin feature#1769
Conversation
Signed-off-by: Sebastian Kawelke <sebastian.kawelke@l3montree.com>
Signed-off-by: Sebastian Kawelke <sebastian.kawelke@l3montree.com>
Signed-off-by: Sebastian Kawelke <sebastian.kawelke@l3montree.com>
Signed-off-by: Sebastian Kawelke <sebastian.kawelke@l3montree.com>
|
Ensure that setting an admin for a sso org is covered |
|
Watch out because of badge api as we would remove the admin token |
|
Ensure to add a feature to change asset slugs |
Signed-off-by: Sebastian Kawelke <sebastian.kawelke@l3montree.com>
|
We also need an admin authed endpoint that confirms a given org exists and return the owner email address of that org. We additionally need an admin authed endpoint that returns for an owner all other orgs this owner owns. |
… getting all external orgs and their admins via endpoint
…o only check each requests signature
|
maybe we should also be able to reset the admin session timer somehow |
TODO
TBD
|
…d remove obsolete indexes and columns
|
@seb-kw currently we pass a limit to the backend when we want e.g. the ecosystem package distribution inside an org. What about if we change the limit to a threshold (relative or absolute?). Instead of "give me the top 10", give me the top 95% or at least 1k components . What do you think about that? |
Ensure CleanupOrphanedRecordsSQL is also callable