Released in v1.0.586
Request configurations can now be configured to depend on the role being requested. For example, if a user is requesting an admin/high-privilege role, you can set up more stringent approval requirements compared to a read-only role.
This is available for all Opal integrations including GitHub, GitLab, and GCP.
Released in v1.0.578
After selecting a requestable item in the Slack modal, the item description will be shown under the dropdown. This will allow users to get more context on what they're requesting.
Available in v1.0.586
Fixes a bug where two GCP compute/sql instances given the same name (but in different projects) would not be able to both be imported into Opal.
Available in v1.0.570
Previously if a resource was selected in the Item to request dropdown, selecting a new app would not refresh the dropdown and cause confusion. Now the state is properly updated.
Fixes a bug where users could assign GCP resource users/groups with no role attached.
Available in v1.0.565
We now support attaching request configurations to multiple groups without duplicating the configuration. If a user is in any of the listed groups, that configuration will be used (according to priority).
Available in v1.0.566
GCP Organizations can now be imported (see docs), allowing users to track and grant organization level roles/users.
Users need to update Opal's service account permissions to include
Available in v1.0.563
Opal's resource "access levels" were renamed to "roles" for clarity and better alignment with our integrations such as GCP, Github, Gitlab etc.
This change does not yet impact APIs
Available in v1.0.563
Previously, Opal would fail to enforce required custom checkboxes in requests. This is now fixed.
Available in v1.0.561
