Open pschisa opened 4 months ago
+1
@pschisa could you clarify what you're looking for here? I'm not sure what Add stored versioning of Teleport roles after edits/changes are made means.
@zmb3 The intention is to maintain a user revision history of the role so that previous saved states of the role can be reviewed and rolled back to as needed.
Thanks, I've updated the title to make this more clear.
In full transparency, this would be a pretty big change and given that you can accomplish this today with IaC workflows involving the Terraform Provider or Kube Operator it's not likely to be picked up soon.
What would you like Teleport to do?
Store prior versions of Teleport roles after edits/changes are made.
What problem does this solve?
Audit of changes made to a role and allows for easy rollback if mistakes are made within a role.
If a workaround exists, please include it.
Use a
tctl get roles
yaml file, terraform provider, or helm operator to manage the role resource to ensure no drift and allow rollback.