...
Code Block | ||
---|---|---|
| ||
GET /zones/18e1f27a-36b5-472f-a03c-6831fb78f97a/adaptors |
Code Block | ||
---|---|---|
| ||
Code Block | ||
| ||
Code Block | ||
| ||
Code Block | ||
|
[10:50]
or… “all of the sub-resources sub resources” e.g. /zones/uuid/users/*73f26990-db53-47fe-a73f-734921ff323d
73f26990-db53-47fe-a73f-734921ff323d73f26990-db53-47fe-a73f-734921ff323d
[10:51]
but if you want to limit which sub-resources can be accessed you need to turn them on/off individually
Robbie Gehbauer
[10:52 AM]
makes sense to me
Mark Fitzpatrick [10:52 AM]
and until we have something like templates, you’ll need to make the appropriate settings when POSTing new resources
[10:53]
and to continue being philosophical…
[10:54]
There are these cases that seem redundant and the behavior needs to be understood e.g.
[10:54]
If a zoneUser has the permissions {
[10:54]
GET /zones/uuid/users
[10:55]
GET /zones/uuid/users/user1-uuid
[10:55]
}
[10:55]
(and say there are three zoneUsers in the zone)
[10:56]
One might think that GET /zones/uuid/users would only return user-1
[10:56]
but it would return all three users
[10:56]
GET /zones/uuid/users/user2-uuid would get an “Access Denied”
[10:57]
...
[
{ ....
"uuid": "7c11c574-0e35-4c78-b572-222952156ac8",
....
},
{ ....
"uuid": "ae91d787-65c9-4f24-bff4-e3acbd6161bb",
....
},
{ ....
"uuid": "ca445ebd-ffcb-4001-9d63-19e773a95fce",
....
}
] |
And detailed access to either adaptor specified in the permissions (ending in ac8 and 1bb) would be allowed but the following request would be denied:
Code Block | ||
---|---|---|
| ||
GET /zones/18e1f27a-36b5-472f-a03c-6831fb78f97a/adaptors/ca445ebd-ffcb-4001-9d63-19e773a95fce |
This allows information about the adaptors to be shared but limits the access to the sensitive registration information about the adaptor.