I am trying to do RBAC implementation for controlling who can edit KVMs. My requirement is that a user role should be able to list/ update/delete ENTRIES in specific KVMs but the role should not be able to create / delete KVMs itself.
e.g. I have defined below permissions against role “kvm-dev-1” so that users in this role group are able to list/ add/ update/delete entries to KVM “TestKVM” in test env.
URL: POST https://api.enterprise.apigee.com/v1/o/{{ORG}}/userroles/kvm-dev-1/resourcepermissions
Request Body: { “resourcePermission”: [ { “path”: “/environments/test/keyvaluemaps/*”, “permissions”: [“get”] }, { “path”: “/environments/test/keyvaluemaps/TestKVM”, “permissions”: [“get”,“put”,“delete”] } ] }
The above is working fine and users in role “kvm-dev-1” are able to add/modify/delete entries in TestKVM through APIGEE management APIs .
Problem: However due to above, the Add /Edit/ Delete Entry buttons against kvm “TestKVM” entries are not visible. I would like to have these buttons on UI rather than asking developers to use management APIs. Any thoughts?