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
It would be helpful from an audit perspective to have which packages are present in the actual operator build. Speaking with @bdunne we can get this list from go build -v, but that would somehow have to come through the operator-sdk build.
This list is useful to start, but ideally, if we can cross reference with the go.sum file, then we can get the versions as well. From there, if we can find a way to cross reference and get the licenses, that would be the most complete manifest. If we can determine where the source comes from, it's possible we might be able to query the license from github (assuming the code is on github).
This issue has been automatically marked as stale because it has not been updated for at least 3 months.
If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.
It would be helpful from an audit perspective to have which packages are present in the actual operator build. Speaking with @bdunne we can get this list from
go build -v
, but that would somehow have to come through the operator-sdk build.This list is useful to start, but ideally, if we can cross reference with the go.sum file, then we can get the versions as well. From there, if we can find a way to cross reference and get the licenses, that would be the most complete manifest. If we can determine where the source comes from, it's possible we might be able to query the license from github (assuming the code is on github).
@miq-bot add-label enhancement
The text was updated successfully, but these errors were encountered: