For our DRA process, we need to produce a CSV of dependencies. This does that, building off a prior PR that had tried to do something similar.
Since I was introducing pip-licenses, I figured I'd go ahead and add a NOTICE.txt file while I was at it. This isn't done, which is why #201 will remain open. We still do not have:
a CI check to make sure all the license are in the green list
automation to provide any license that pip-licenses cannot find
a CI check to make sure that any new deps added were also added to the NOTICE file
However, these are outside the scope of the current project, which is to expeditiously provide a CSV. We can iterate later.
Checklists
Pre-Review Checklist
[x] this PR does NOT contain credentials of any kind, such as API keys or username/passwords (double check config.yml.example)
[x] this PR has a meaningful title
[x] this PR links to all relevant github issues that it fixes or partially addresses
[x] this PR has a thorough description
[x] Tested the changes locally
[x] Added a label for each target release version (example: v7.13.2, v7.14.0, v8.0.0)
Part of https://github.com/elastic/search-team/issues/8047
Relates to https://github.com/elastic/connectors/issues/201
For our DRA process, we need to produce a CSV of dependencies. This does that, building off a prior PR that had tried to do something similar.
Since I was introducing
pip-licenses, I figured I'd go ahead and add a NOTICE.txt file while I was at it. This isn't done, which is why #201 will remain open. We still do not have:pip-licensescannot findHowever, these are outside the scope of the current project, which is to expeditiously provide a CSV. We can iterate later.
Checklists
Pre-Review Checklist
config.yml.example)v7.13.2,v7.14.0,v8.0.0)