You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of having a separate view (and class?) for workspace sharing audits and auth domain membership audits, it might be possible to run both audits in one. This would also make it easier to add other audits, like checking for requester pays (except that doesn't have a group).
Considerations:
The audit class for a workspace type would run both a sharing audit and an auth domain membership audit for each workspace.
The results classes know how to handle their results, so we would just have to call the handle() method somewhere.
Tables would have to chance somehow: in the sharing case the table shows access level and compute status, and in the auth domain case it shows role. It would be less straightforward to combine these into a single table.
The way that we showing the "action" button in the table would need to change because right now the view we are accessing is hardcoded into the template. This could probably be updated by adding a method or attribute that gets the view responsible for handling the action (e.g., "get_handle_view_name" or "handle_view_name"), and using that in the template or table.
The text was updated successfully, but these errors were encountered:
Instead of having a separate view (and class?) for workspace sharing audits and auth domain membership audits, it might be possible to run both audits in one. This would also make it easier to add other audits, like checking for requester pays (except that doesn't have a group).
Considerations:
The text was updated successfully, but these errors were encountered: