Reworked 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.

Fixes 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.

Fixed a bug that caused the default request expiration time to not properly match the maximum and recommended durations in the corresponding request configuration.

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.

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.

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.