I like the idea but what will it really mean to turn off use_self_service. I know it will mean tenancy will be disabled and API permissions won't be checked against a user's capabilities, but will the self-service stuff rob butts is working on be affected in any way? Will self-service truly be turned off via a parameter?
IMO it would be nice if TC 3.0 made tenancy / roles & capabilities a requirement. No more turning it on and off. The scope of what you see is dictated by your tenancy and the api's that you have access to are dictated by your capabilities. Jeremy On Thu, Jun 14, 2018 at 11:49 AM, Volz, Dylan <[email protected]> wrote: > Hi Traffic Controllers, > > I am working on enforcing the roles->capabilities system as a replacement > for the soon-to-be legacy priv level system. Like tenancy this is a feature > moving us towards self-service; so to minimize our code/behavior paths > I would like to propose renaming the use_tenancy parameter to > use_self_service, so that if it is turned on both tenancy and capabilities > are applied. This prevents some hairy cases arising when capabilities are > on and tenancy is off or vice versa. Let me know if you have any questions, > concerns, or suggestions. > > Thanks, > Dylan >
