stable

Clone or download

Read-only

Add service level permissions for FRS

This introduce a new project level route /projects/:id/frs_service There was several possibilities for this: - add the information in existing 'resources' in /projects/:id route But this was odd because some resources would have perms (or any top level metadata) whereas some others would not. - add in 'extra_informations' in the very same route but it's already kind of mess there. As FRS (or docman, or even later trackers) are services with real data attach to them, it makes sense to have a project level route dedicated to them. Part of story #13654 have detailed permissions in REST API Change-Id: Ic4389afe5b814ae85927f8e3b3e7176e996d7185

Modified Files

Name
M plugins/frs/include/FRS/REST/ResourcesInjector.php +2 −0 Go to diff View file
M plugins/frs/include/FRS/REST/v1/ProjectResource.php +37 −0 Go to diff View file
A plugins/frs/include/FRS/REST/v1/ServicePermissionsForGroupsRepresentation.php +53 −0 Go to diff View file
A plugins/frs/include/FRS/REST/v1/ServiceRepresentation.php +41 −0 Go to diff View file
A plugins/frs/include/FRS/REST/v1/ServiceRepresentationBuilder.php +93 −0 Go to diff View file
A plugins/frs/phpunit/FRS/REST/v1/ServiceRepresentationBuilderTest.php +174 −0 Go to diff View file
M plugins/frs/tests/rest/FRS/PackagesTest.php +14 −0 Go to diff View file
A plugins/frs/tests/rest/FRS/ServiceTest.php +83 −0 Go to diff View file