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.
A 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.
Reworked how Opal handles access to GCP SQL instances. We now better match how the GCP console behaves:
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.
Available 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.
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.