-
Notifications
You must be signed in to change notification settings - Fork 321
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
Sig4v go.mod has not been tagged or released since inception #709
Comments
BTW I discovered this with the following use-case which I don't think should be considered "external": to use the sigv4 implementation in this module in order to create a Prometheus client. This is namely the only reasonable way to connect to AMP (AWS Managed Prometheus) Prometheus API without implementing it all by hand. Such implementation looks roughly like this:
I can get around it by running |
Looking at this module, I would recommend the following. I tag here @SuperQ as he's the last one to change the subpackage I have done some more digging and found out the following:
In view of all of these, I'd recommend the following:
Please let me know what you think. I may be able to participate in this effort. |
I agree, we have quite a number of issues with the current setup. I would like to split the repo. |
Thank you @SuperQ . I am not a member of the org. How can we get it going? |
fine to me |
Initial code copy: prometheus/sigv4#1 |
https://github.com/prometheus/sigv4/releases/tag/v0.1.0 is now released. |
Migrate use of prometheus/common/sigv4 to prometheus/sigv4. Related to: prometheus/common#709 Signed-off-by: SuperQ <[email protected]>
Mark the sigv4 module deprecated in favor of the new repo location. * https://github.com/prometheus/sigv4 Closes: #709 Signed-off-by: SuperQ <[email protected]>
Migrate use of prometheus/common/sigv4 to prometheus/sigv4. Related to: prometheus/common#709 Signed-off-by: SuperQ <[email protected]>
Migrate use of prometheus/common/sigv4 to prometheus/sigv4. Related to: prometheus/common#709 Signed-off-by: SuperQ <[email protected]>
Migrate use of prometheus/common/sigv4 to prometheus/sigv4. Related to: prometheus/common#709 Signed-off-by: SuperQ <[email protected]>
The sigv4 README states the following:
This is a separate module from github.com/prometheus/common to prevent it from having and propagating a dependency on the AWS SDK
.This module is considered internal to Prometheus, without any stability guarantees for external usage.
The problem is that any attempt to import the
github.com/prometheus/common/sigv4
package and runninggo get -u ./...
brings over the dependencygithub.com/prometheus/common/sigv4 v0.1.0
which is thego.mod
file of this module since its inception - 2021-06-23.This module has not been tagged ever since.
As a result, even Prometheus itself is not using any of the changes to this module since the original tagging!
prometheus/prometheus go.mod
has the same
github.com/prometheus/common/sigv4 v0.1.0
dependency.Please tag and release this module on a regular basis. Thank you!
(Alternatively you can split this module out to a separate repository if this does not create circular dependency issues).
The text was updated successfully, but these errors were encountered: