[
https://issues.apache.org/jira/browse/TC-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15950978#comment-15950978
]
Ryan Durfey commented on TC-217:
--------------------------------
I believe that would work. I think there are always two cases. First, the
default, assume all work is to be done directly under your current tenant
assignment. Second, specify a tenant ID (which must be below you) under which
you want to perform an action. I am open to forcing the user to always pass a
tenant ID with the operation if that makes more sense. I will add this
discussion to the wiki, but below are my initial thoughts.
Create:
-Default: Create a tenant below your user assigned tenant
-Pass an ID with create for a tenant below your assignment under which you want
the new tenant created.
Read:
-Get a list of all tenants below your user tenant assignment
-Pass a tenant ID with read to read all tenants below a specified tenant below
your assignment
Update:
-Update a parameter on your current tenant
-Pass a tenant ID with update to modify a parameter on a specified tenant below
your assignment
Delete:
-Can't delete your assigned tenant since it would leave your user orphaned,
must be done by a user assigned to a tenant above you.
-Pass a tenant ID with delete to remove a specified tenant below your assignment
-May need to put guard rails on this to not allow deletes of tenants which have
active users or services.
> 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)
