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
Hello, I am currently using the PrismaCloud API. I am using three entry-points: hosts, images and registry. On those calls, I am using a filter on the collection, as "collections": "All". However, I see a different behaviour on hosts and images.
On the host case, when fetching with a collection filter on All, the api returns me all the assets that match the filter and enumerate for each asset, all the collection associated. As an example, for a given asset, I will have a list of collection as: "collections": [ "All", "resource_1"].
However, I suspect a different behaviour on the image entry-point. Indeed, I apply again a filter on the collection, here All, but instead of having the list of all the collection, for a given asset, I will only have the filtering one, here All. So if I have an asset, with multiple collection associated, in the returned data of the API, I will only have "collections": ["All"].
Suggested fix
I would like to know if it is the expected behaviour of the API, or is it possible to have for a given asset, all the associated collections. Thanks for your help.
The text was updated successfully, but these errors were encountered:
Documentation link
Describe the problem
Hello, I am currently using the PrismaCloud API. I am using three entry-points: hosts, images and registry. On those calls, I am using a filter on the collection, as
"collections": "All"
. However, I see a different behaviour on hosts and images.On the host case, when fetching with a collection filter on
All
, the api returns me all the assets that match the filter and enumerate for each asset, all the collection associated. As an example, for a given asset, I will have a list of collection as:"collections": [ "All", "resource_1"]
.However, I suspect a different behaviour on the image entry-point. Indeed, I apply again a filter on the collection, here
All
, but instead of having the list of all the collection, for a given asset, I will only have the filtering one, hereAll
. So if I have an asset, with multiple collection associated, in the returned data of the API, I will only have"collections": ["All"]
.Suggested fix
I would like to know if it is the expected behaviour of the API, or is it possible to have for a given asset, all the associated collections. Thanks for your help.
The text was updated successfully, but these errors were encountered: