We should review the following edge case issues and decide which ones are worth fixing (and opening a Jira card) and which are not:

1. Impossibility to filter by gcp_project with RBAC access set to all GCP accounts (unless we specify permissions for specific gcp projects)

• it is a similar issue to OCP cluster/node RBAC inheritance issue we have fixed (COST-4764)
• it’s a different issue than COST-4990
• affects the UI

2. We still miss RBAC support for cost categories resource type endpoint (ui typeahead)

• it was originally reported in COST-3831, then closed in favor of COST-3471, but not sure if it was even considered for implementation (based on comments, the issue COST-3471 was about something else)
• affects the UI

3. we can't use filtering with AND on OCP on ALL endpoint

• this works (ocp on aws): http://localhost:8000/api/cost-management/v1/reports/openshift/infrastructures/aws/costs/?filter[and:project]=test
• this doesn't work (ocp on all): http://localhost:8000/api/cost-management/v1/reports/openshift/infrastructures/all/costs/?filter[and:project]=test
• probably not used in the UI

{ 
    "filter": {
        "and:project": ["Unsupported parameter or invalid value"] 
    }
} 

4. Filtering by aws account on ocp on all endpoint doesn't work with RBAC

• not used in the UI