Jira (PDB-4679) PuppetDB 5.2.13 keep v1 metrics available

[Bouke Haarsma (Jira)]

Bouke Haarsma created an issue

PuppetDB / PDB-4679 PuppetDB 5.2.13 keep v1 metrics available Issue Type: Bug Affects Versions: PDB 5.2.13 Assignee: Unassigned Components: PuppetDB Created: 2020/03/28 12:43 AM Priority: Normal Reporter: Bouke Haarsma PuppetDB Version: 5.2.13 OS Name/Version: CentOS 7.4 When upgrading to 5.2.12 the v1 metrics endpoint is disabled to mitigate CVE-2020-7943. However this causes an issue for an application we're using (puppetboard 1.0) that doesn't support v1 endpoint. There's a new major version of puppetboard that supports the v2 endpoint, but requires us to upgrade to Python 3. This basically means upgrading a whole lot of components, which we would like to do some other time. Therefor, we would like some option to enable the v1 endpoint in PuppetDB 5.2.13, to keep existing applications working. Desired Behavior: PuppetDB 5.2.13 should have a v1 metrics endpoint. Actual Behavior: PuppetDB 5.2.13 disables the v1 metrics endpoint.   Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

[Zachary Kent (Jira)]

Zachary Kent commented on PDB-4679

Re: PuppetDB 5.2.13 keep v1 metrics available Apologies for the delayed response. A work around to manually enable v1 metrics can be found in the comments of PDB-4876. We're going to be updating our documentation to reflect this.

Add Comment