In metabase, one can create collections inside collections, and there is no unique name constraint as metabase keeps track of collection id rather than name itself.
# metabase collections
- Our Analytics
- Sample Collection
- CabFares
- DS Analysis
- Summary
- Spending
- Countries
- DS Analysis
If we add this metabase as a provider in existing guardian... when fetching resources (api endpoint: api/v1beta1/resources?provider_type=metabase
), it returns the following response. In this, based on name - one cannot identify which collection it is - the one under CabFares
or the one under Spending
.
One can identify using the urn
(collectionid), but it not understandable for a user when raising appeal which one to request for - unless they know the collectionId. Hence, the information is insufficient or unclear
{
"resources": [
{
"id": "b1f0d1dc-afda-4e3f-8fcf-0f2167bf4aba",
"provider_type": "metabase",
"provider_urn": "odpf-metabase",
"type": "collection",
"urn": "collection:14",
"name": "DS Analysis",
"details": { ... },
"created_at": "2022-06-23T08:00:07.035136Z",
"updated_at": "2022-06-23T16:00:07.018758Z"
},
{
"id": "98c4bf30-f021-49cc-927f-6e01ce5210ce",
"provider_type": "metabase",
"provider_urn": "odpf-metabase",
"type": "collection",
"urn": "collection:16",
"name": "DS Analysis",
"details": { ... },
"created_at": "2022-06-06T08:37:38.681177Z",
"updated_at": "2022-06-23T16:00:07.018758Z"
}
...
]
}