Closed micahhausler closed 1 year ago
/remove-label do-not-merge/hold
@micahhausler: The label(s) /remove-label do-not-merge/hold
cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor
. Is this label configured under labels -> additional_labels
or labels -> restricted_labels
in plugin.yaml
?
/remove-label hold
@micahhausler: The label(s) /remove-label hold
cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor
. Is this label configured under labels -> additional_labels
or labels -> restricted_labels
in plugin.yaml
?
Thanks @micahhausler ! It needed a refactor badly, it grew to the current Frankenstein slowly over the years and I had my eye on it for a while.
/lgtm /approve /hold cancel
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: cpanato, micahhausler, puerco, saschagrunert
The full list of commands accepted by this bot can be found here.
The pull request process is described here
This change starts to move individual OS type logic out to individual implementations and files.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This change will make it easier to write and test new OS types for
bom generate --scan-images
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
I tried to keep the
osinfo
package API as close to the same as possible. I made thecontainerScanner
andlayerScanner
interfaces and their implementations internal to the package as they're not currently used externally.Does this PR introduce a user-facing change?