Page MenuHomeFreeBSD

net-mgmt/pushgateway: Update to 1.3.1
ClosedPublic

Authored by rhurlin on Dec 28 2020, 8:09 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Jun 17, 5:35 AM
Unknown Object (File)
Mon, Jun 3, 1:07 AM
Unknown Object (File)
Thu, May 30, 12:14 PM
Unknown Object (File)
Thu, May 30, 12:14 PM
Unknown Object (File)
Thu, May 30, 11:01 AM
Unknown Object (File)
May 9 2024, 3:24 PM
Unknown Object (File)
May 9 2024, 3:24 PM
Unknown Object (File)
May 9 2024, 3:24 PM
Subscribers

Details

Summary

Update from 0.10.0 to 1.3.1 (skips v1.0.0, v1.0.1, v1.1.0, v1.2.0, and v1.3.0) [1].

  • [CHANGE] Remove code to convert the legacy v0.5--v0.9 storage format
  • [FEATURE] Add an HTTP API to query pushed metrics and runtime information
  • [FEATURE] Add Docker image build for ppc64le architecture
  • [FEATURE] Add flag --push.disable-consistency-check
  • [ENHANCEMENT] Logging: Show remote address when failing to parse pushed metrics
  • [ENHANCEMENT] Remove excessive whitespace from HTML templates
  • [ENHANCEMENT] Web UI: Add scroll bare to list of pushed metrics
  • [ENHANCEMENT] Web UI: Improved metrics text alignment
  • [BUGFIX] Fix docker manifest files for non-amd64 architectures
  • [BUGFIX] Web UI: Fix deletion of groups with empty label values
  • [BUGFIX] Web UI: Update JQuery to v3.5.1 to address security concerns

[1] Changelogs: https://github.com/prometheus/pushgateway/releases

The last committed ports version 0.10.0 [2] was necessary, because it changed the storage format. Users got about 4 weeks to migrate their old data format.

[2] https://reviews.freebsd.org/D27165

I am not sure, if v1.3.1 should also get its way into the Quarterly Branch per MFH before end of year 2020?

Submitted by Gabriel Dutra <0xdutra@gmail.com> (maintainer) in PR 251229.

Tested on Poudriere (amd64, i386). 'portlint -AC' is fine.

Diff Detail

Repository
rP FreeBSD ports repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Dec 28 2020, 12:10 PM

Thanks for the fast response.

One last question: Should I also add MFH: 2021Q1 in the commit? We MFH'd v0.10.0 into 2020Q4, because users should get the possibility to migrate their data before version >= 1.0.0 ...

This revision was automatically updated to reflect the committed changes.