-
Notifications
You must be signed in to change notification settings - Fork 84
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
photon support #129
photon support #129
Conversation
ping. |
Very cool. Ill pull down your code and confirm its working today. Sorry for the delay! |
looks good so far. indexing seems correct. However we are running into a bug that's been fixed in latest release. Can you please rebase this branch onto of master. |
6a116c2
to
cdbfcf3
Compare
Thank you @ldelossa Rebased. |
@ppadmavilasom cool, re-checking |
fyi. this is what i have done to validate while developing (from the photon folder) |
@ppadmavilasom it would be good to obtain an IndexReport from the api and give it a spot check. That is what I am doing just to confirm json schemas look good. |
something is a little funky. packages are not being linked with distributions. Using your branch you can see that Ubuntu links correct
|
Plz apply this patch:
|
- add support for Photon OS versions 1, 2 and 3 - uses oval files published at https://packages.vmware.com/photon/security/oval/
cdbfcf3
to
4b8de45
Compare
@ldelossa i ran top level tests as well. i will check missing distribution_id maps manually (dont see tests covering it) |
@ppadmavilasom I provided a patch. we missed the inclusion of your distribution scanner in the rpm ecosystem. Ecosystem is just a way for us to group constructors for used during the indexing of a image. |
@ldelossa Thanks! included the patch for ecosystem and added missing libvuln/updaters |
@ppadmavilasom looks good! |
Awesome. thank you. |
4b8de45
to
cabfd25
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Continuing the discussion from #118
@ldelossa please advice further steps required