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
Update dependencies #32
Update dependencies #32
Conversation
any comment on this @benjaminguttmann-avtq ? |
@chitoku-k like last time, would appreciate to maybe have a dedicated PR for the README as it is not related to the dependency update, but you can leave it like that :D Thank you for doing the work, I will test the same and if successful approve it |
44f502f
to
603f30e
Compare
@benjaminguttmann-avtq Sorry about that. I've just moved them to #33. |
Hi @chitoku-k, sorry I was very busy in the last months :-/ Finally having time to give this one a try. I guess you tried to build a binary out of your branch, right? I just tried to 'go get' it and get the following result:
Sorry, not that familiar with go, so maybe it is just me doing something wrong here. |
@benjaminguttmann-avtq |
@chitoku-k I merged it to make it easier for me to test the build with promu but it seems like I still get some error there. Maybe you can support me on this. What I am trying to do is run When executing I receive the following:
|
Okay, after I adjusted the .promu config to use flag mod=mod instead of vendor I bypassed those issues. filters/deployments_filter.go:9:2: module github.com/prometheus/common@latest found (v0.37.0), but does not contain package github.com/prometheus/common/log So I guess that needs to get replaced everywhere >.< |
What I found is that Makefile also needs to be modified. Opening PR... |
Try #34! |
Hi, thanks for developing and maintaining bosh_exporter!
As the dependencies of bosh_exporter have become too old for now, any further maintenance becomes somewhat harder. This PR tries to bump them as latest as possible to address that. Apart from that, I am trying to add some features to help service discovery better work with certain environments by exposing their CIDs in the future time :)