-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prevent Elastic-licensed code from leaking into OSS distributions #38719
Labels
needs_team
Indicates that the issue/PR needs a Team:* label
Comments
botelastic
bot
added
the
needs_team
Indicates that the issue/PR needs a Team:* label
label
Apr 3, 2024
This issue doesn't have a |
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this issue
Apr 3, 2024
According to LICENSE.txt, the Beats project uses both Apache 2.0 (OSS) and Elastic licenses. The OSS code may not depend on the Elastic License code otherwise the OSS-only binaries become tainted. This makes golangci-lint emit warnings for OSS code that depends on x-pack code. Closes elastic#38719
6 tasks
PR: #38720 |
andrewkroh
added a commit
that referenced
this issue
Apr 4, 2024
According to LICENSE.txt, the Beats project uses both Apache 2.0 (OSS) and Elastic licenses. The OSS code may not depend on the Elastic License code otherwise the OSS-only binaries become tainted. This makes golangci-lint emit warnings for OSS code that depends on x-pack code. Closes #38719
zeynepyz
pushed a commit
to zeynepyz/beats
that referenced
this issue
Apr 7, 2024
According to LICENSE.txt, the Beats project uses both Apache 2.0 (OSS) and Elastic licenses. The OSS code may not depend on the Elastic License code otherwise the OSS-only binaries become tainted. This makes golangci-lint emit warnings for OSS code that depends on x-pack code. Closes elastic#38719
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Beats projects releases OSS-only artifacts (e.g. filebeat OSS-only). These artifacts should not contain code or features that have an Elastic license (aka "x-pack" code for legacy reasons). The project should have enforcement that there are no dependencies from OSS code to x-pack code.
This can be enforced with depguard check. For example:
The current state is that there is a single violation:
References
The text was updated successfully, but these errors were encountered: