pjfanning opened a new pull request, #261:
URL: https://github.com/apache/openserverless/pull/261

   Part of #260.
   
   The top-level `LICENSE` credits ingress-nginx, Kubegres, openshift-acme, 
Prometheus / kube-state-metrics and the OpenWhisk Helm chart, but each entry 
names only the copies under `oplugins/`. The source release (checked against 
`apache-openserverless-0.9.0-incubating-src.tar.gz`, RC7) also ships copies of 
the same components under `oplugins-op/` and `testing/`. This PR adds those 
paths to the existing entries:
   
   - **ingress-nginx**: 3 manifests in `oplugins-op/deploy/ingress-nginx/` 
(controller v1.8.1 and v1.5.1, versions LICENSE did not mention) and 
`testing/stress-test/oplugins-stress/setup/docker/ingress-deploy.yaml` 
(v1.7.0). The entry is now grouped by controller version.
   - **Kubegres**: the CRD, roles and common descriptors in 
`oplugins-op/deploy/openserverless-permissions/` and 
`testing/stress-test/oplugins-stress/setup/kubernetes/`, plus the operator 
deployment `oplugins-op/deploy/postgres-operator/kubegres-operator.yaml` 
(Kubegres 1.18).
   - **openshift-acme**: `oplugins-op/deploy/acme-openshift/`.
   - **Prometheus and kube-state-metrics**: `oplugins-op/deploy/monitoring/*` 
and the monitoring service accounts / roles in 
`oplugins-op/deploy/openserverless-permissions/`.
   - **OpenWhisk Helm chart descriptors**: the 19 files under `oplugins-op/` 
and `testing/` that carry `# Source: openwhisk/templates/...` comments.
   
   Every path listed exists in the RC7 source tarball. LICENSE-only change; no 
code changes.
   
   Not covered here (still open in #260): components missing from LICENSE 
entirely (mvdan/sh, cert-manager, Milvus, milvus-operator, Locust), and the ASF 
headers on vendored third-party files.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to