-
Notifications
You must be signed in to change notification settings - Fork 80
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
can you provide binaries for different architectures? #21
Comments
hey @BartVerc , could you look into this? |
@bastelfreak It's possible that we could investigate adding goreleaser support to this project to provide binaries. |
I'm also interested in this. I've depended on the amd64 binaries being there at |
@debugloop I'll bring this up during planning today. |
@pgporada Thank you. As a work around I've forked the repo temporarily and created a release with a build myself and I've noticed another small issue thats somewhat related: The most recent release v0.3 uses the old module path, i.e. it does not build without a hitch. It's probably the simplest solution to draft a new minor or bugfix release with the current path and maybe address this issue (lack of binaries) while at it. Best regards and thanks to the rest of the team too :) |
Hi!
thanks for the great software! I maintain https://github.com/voxpupuli/puppet-prometheus, which is a puppet module to manage many different exporters. I would like to add support for your unbound_exporter as well, but that requires binarys that I can fetch from github. Any chance you can add them to your latest release?
The text was updated successfully, but these errors were encountered: