AzBuilder / terrakube

Open source IaC Automation and Collaboration Software.
https://docs.terrakube.io
Apache License 2.0
496 stars 38 forks source link

Additional role in org (to protect the state) #1245

Closed stanleyz closed 3 days ago

stanleyz commented 3 weeks ago

Feedback

Currently, a user in an organization needs to have Manage Workspace permission to create new jobs, aka. run Terraform, but once the user has this permission, who can change all the settings of the workspace, is it possible to have a separate role to allow users to "use" the workspace but not manage it? Operations that are potentially in the use category could include:

  1. Run Terraform from CLI
  2. Issue a Run from UI

but not include:

  1. Update any settings of the workspace
  2. Read the state of the workspace
  3. Pull (dump out) the workspace state to local

The thinking behind this is that the state file could include sensitive data that we don't want all users to read and that users of the workspace should not have the ability to update settings such as IaC version, template etc.

Potential work included in the above suggestion:

  1. A new role (Use workspace maybe)
  2. Enhancement to UI to disable state file output and settings of the workspace.