You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PyTerraBackTYL should have the option to require user authentication to get and set data.
Requirements:
Like persistent and non-persistent backends, this should be a user-configurable plugin.
The default should be an LDAP/AD lookup
Ideas for consideration as a requirement:
Pass the module to the non-persistent backends
Functionality to glob on ENV so that some environments will require auth (e.g. prod) and some will not (e.g. non-prod).
Boolean config option to enable checking by PyTerraBackTYL
when set to False, it would become the duty of the persistent backend to perform this task
The module should be passed to the persistent backend
Passing the auth module to the backend and the globing on the ENV would be two different ways of allowing ENV based auth requirements and are not wholly compatible.
this ticket a work-in-progress. Documentation updates still need to be listed.
The text was updated successfully, but these errors were encountered:
Some light RBAC would also be nice . . . this could allow read-only access to the state file for users - allowing them to run a plan - and write-access for admins allowing them to run apply
PyTerraBackTYL should have the option to require user authentication to get and set data.
Requirements:
Ideas for consideration as a requirement:
this ticket a work-in-progress. Documentation updates still need to be listed.
The text was updated successfully, but these errors were encountered: