-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Add a homebrew tap release for ocb #5680
Comments
I think @tigrannajaryan (and perhaps @codeboten) holds the keys to bots and similar accounts. They would be the right folks to create and set the right credentials. I would probably help if you could point them exactly what they would need to do (ie, create an account here, generate an API key, add the API key as |
The TC usually manages secrets. However, we don't have any for homebrew and I don't know what ocb is. If someone takes the responsibility to do the work I can help with secret management. |
@tigrannajaryan ocb == OpenTelemetry Collector Builder. I like the idea of adding ocb to homebrew. If the outcome of the discussion around whether or not Contrib should really be used in production is that it should not, the ocb's importance increases. Being able to install it via homebrew is a nice option. |
Update the goreleaser configuration so that ocb releases will automatically update the OpenTelementry Homebrew tap. This fixes open-telemetry#5680. Signed-off-by: James Peach <jpeach@cloudflare.com>
Can we close this issue @TylerHelmuth @jpeach @jpkrohling since the outcome was to add the release to the core homebrew? |
Is your feature request related to a problem? Please describe.
Make ocb easier to install and update to the latest release.
Describe the solution you'd like
Add a Homebrew tap release for ocb. goreleaser supports releasing to a tap, so I don't think the per-release overhead would be much work. We would need a
open-telemetry/homebrew-tap
repository to release into, and possibly some access changes to bot accounts.I'm happy to help get this done, though I expect to need some maintainer support for github configuration changes.
The text was updated successfully, but these errors were encountered: