Closed elichad closed 4 years ago
Further items:
dataset_locks will always include an rse_id
api/rule - access_rule permission only fails if the VO doesn't match - so the message is ok, but change the name of the permission to reflect this - as part of #75
rucio_vo_sqlite.cfg
->rucio_multi_vo_sqlite.cfg
rucio.cfg.template
and add a multi-VO template instead e.g.rucio_multi_vo.cfg.template
/vos
not/vo
(both in dev and travis)get_replica_locks_for_rule_id
- return empty list if rule VO doesn't match issuer, to avoid giving away that the rule exists on a different VO. Move the current error message to debug log.rucio_loadhook
-auth.get('vo')
to fall back on 'def'get_global_account_limits
allowsaccount=None
, but API does not account for this. Apply VO limit at API level as for other account functions