Fixes an issue where syncing AWS RDS instances would sometimes result in an error showing "invalid RDS instance arn".
Scope Down GCP Roles List
by AdrianPreviously, Opal would list all available roles in all resource types when users add new custom roles. However, some roles cant be applied to certain resource types, or some can only be applied to certain resource types, etc. We now will properly show only relevant roles which can actually be applied to the resource being viewed.
Remove Accidental GCP Role Ingestion
by AdrianA bug had caused Opal to ingest more roles than necessary for GCP resources during a certain period of time. To remedy this, we are deleting custom roles ingested during this time period.
Rework GCP SQL Instance Access
by AdrianReworked how Opal handles access to GCP SQL instances. We now better match how the GCP console behaves:
- Roles are no longer inherited into SQL instance resources.
- The SQL instance user list now purely represents the list of users who have been added to the instance, with no role assignment.
- Adding a user to an SQL instance in Opal also adds the Cloud SQL Instance User role to that user in that instance's parent project.
- Removing a user from an SQL instance in Opal does not remove the Cloud SQL Instance User role from that user.
Fix Import Bug On App Creation
by AdrianFixes a bug where when first adding an app/integration, all resources could be imported to Opal even if the import setting is set to manual imports.
Fix default request expiration bug.
by AdrianFixed a bug that caused the default request expiration time to not properly match the maximum and recommended durations in the corresponding request configuration.
Fixed issue with scrolling in Access Review users
by Tim MickelAvailable in 1.0.587
Scrolling the Access Review table would sometimes have jumps/glitches when user details were expanded. This is now fixed
Released in v1.0.584
Events on an access request page can now be sorted by time. Additionally, the default sorting now shows the most recent events at the top.
Condition request configurations based on role
by Tim MickelReleased 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.