v2.8.0

v2.8.0 - 2024-10-10

dependency

• Upgrade go to 1.23.2

🚀 Enhancements

• Upgrade integrations SDK so the interval is variable and allows intervals up to 5 minutes

v2.7.7

v2.7.7 - 2024-09-12

⛓️ Dependencies

• Updated golang version to v1.23.1

v2.7.6

v2.7.6 - 2024-07-04

⛓️ Dependencies

• Updated golang version to v1.22.5

v2.7.5

v2.7.5 - 2024-05-09

⛓️ Dependencies

• Updated golang version to v1.22.3

v2.7.4

v2.7.4 - 2024-04-11

⛓️ Dependencies

• Updated golang version to v1.22.2

v2.7.3

v2.7.3 - 2024-02-22

⛓️ Dependencies

• Updated github.com/newrelic/infra-integrations-sdk to v3.8.2+incompatible

v2.7.2

v2.7.2 - 2023-10-26

⛓️ Dependencies

• Updated golang version to 1.21

v2.7.1

Fixed 🐛

• Removes config validation that prevents to run the integration without a custom CA certificates (#71)

v2.7.0

What's Changed

• chore: disable CGO by @sigilioso in #63
• chore: Update Go version to 1.20 by @gsanchezgavier in #67

Full Changelog: v2.6.0...v2.7.0

v2.6.0

What's Changed

• Updating golang to 1.18, adding workaround for commonName deprecation by @paologallinaharbur in #56

Breaking

In the new golang version the CommonName is no longer taken into consideration while validating certificates.

The deprecated, legacy behavior of treating the CommonName field on X.509 certificates as a host name when no Subject Alternative Names are present is now disabled by default.

This could be an issue for users still relying on legacy commonName and not on Subject Alternative Name. In that case they would see an error message like:

[ERR] Encountered fatal error: Post [...] x509:  certificate relies on legacy Common Name field, use SANs instead

To overcome this issue the user should update the certificate relying on Subject Alternative Name.
While the certificate is not updated, certificate validation could be disabled setting --tls_insecure_skip_verify to true.

Full Changelog: v2.5.3...v2.6.0