Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue/Help with "Get Image Scan Results" #593

Open
RegisGraptin opened this issue Jan 31, 2024 · 0 comments
Open

Issue/Help with "Get Image Scan Results" #593

RegisGraptin opened this issue Jan 31, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@RegisGraptin
Copy link

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, 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.

@RegisGraptin RegisGraptin added the documentation Improvements or additions to documentation label Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant