[
https://issues.apache.org/jira/browse/TC-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15973263#comment-15973263
]
Jeremy Mitchell commented on TC-217:
------------------------------------
[~orifinkelman] - i would prefer to stay away from nested json if possible. is
a list like this possible from GET /api/../tenants and GET
/api/.../tenants/:id/subtenants
[
{ id: 1, name: root, parent: null },
{ id: 2, name: tenant-1, parent: 1 },
{ id: 3, name: tenant-1-child-1, parent: 2 },
{ id: 4, name: tenant-1-child-1-child, parent: 3 },
{ id: 5, name: tenant-1-child-2, parent: 2 },
{ id: 6, name: tenant-2, parent: 1 },
{ id: 7, name: tenant-2-child-1, parent: 6 },
]
see how it's a "flat" list of hashes....but they are ordered based on their
relationship to one another...
> Self Service - CRUD Sub Tenant
> ------------------------------
>
> Key: TC-217
> URL: https://issues.apache.org/jira/browse/TC-217
> Project: Traffic Control
> Issue Type: New Feature
> Components: Traffic Ops, Traffic Ops API
> Reporter: Ashish Timilsina
>
> Allow users to CRUD sub tenants below their tenant level or below any
> sub-tenant level they choose. Default would be directly below the current
> tenant value.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
