Hey Michael,

Can we remove the elastic search configuration from oom that indicates "Not free for commercial use"?

Thanks,
Mike.
The primary findings requiring action from the latest scan is highlighted in red or yellow on the summary tab:
• ccsdk: In ccsdk-dashboard, there is a JavaScript file which contains non-open source code subject to "GreenSock Terms of Use". Please see my comments in the "Use restrictions" tab.
• oom: In oom, there is a configuration file which appears to make use of Elasticsearch features that are labeled as "Not free for commercial use". Please see my comments in the "Use restrictions" tab.
• integration-benchmark: there are 15 CSAR files containing text files marked as "proprietary or restricted". These are listed in the "Use restrictions" tab. These files should be removed, and/or replaced with alternatives that do not contain these notices.
• ccsdk-distribution and ccsdk-features: These repos have had 7 EPL-1.0 files added, which are under a weak copyleft license. These are listed in the "Copyleft" tab. Is it possible to remove and replace these with Apache-2.0 or permissively-licensed alternatives?
• ccsdk-features: There are 10 package.json files within the "odlux" subfolder which list their license as "MIT". These are listed in the "Check license statement" tab. If these are original to ONAP, this should be "Apache-2.0" instead.
• vid: Same comment, there is 1 package.cypress.json file which should be reviewed – if it is original to ONAP, it should likely be "Apache-2.0" instead.