v4.0.5

✨ built with go1.18
As part of bumping to Go 1.18 certificates that are signed with the SHA-1 hash function will no longer be accepted.

What's Changed

• Bump actions/checkout from 2 to 3 by @dependabot in #74
• Bump dependabot/fetch-metadata from 1.1.1 to 1.3.0 by @dependabot in #75
• Bump actions/setup-go from 2 to 3 by @dependabot in #77
• Bump github.com/onsi/gomega from 1.18.1 to 1.19.0 by @dependabot in #72
• golang version 1.18.0

Full Changelog: v4.0.4...v4.0.5

v4.0.4

✨ built with go1.18

What's Changed

• Bump github.com/onsi/ginkgo from 1.12.0 to 1.16.5 by @dependabot in #63
• Bump github.com/onsi/gomega from 1.9.0 to 1.18.0 by @dependabot in #64
• Bump github.com/jessevdk/go-flags from 1.4.0 to 1.5.0 by @dependabot in #60
• Bump github.com/onsi/gomega from 1.18.0 to 1.18.1 by @dependabot in #65
• Bump code.cloudfoundry.org/cli from 6.40.1+incompatible to 7.1.0+incompatible by @dependabot in #62

New Contributors

• @ctlong made their first contribution in #59
• @dpage-pivot made their first contribution in #51
• @dependabot made their first contribution in #63

Full Changelog: v4.0.3...v4.0.4

Log Cache CLI 4.0.3

• Built with Go 1.17.5

⚠️ IPv4 addresses containing decimal components with leading zeros will be rejected

With the upgrade to Go 1.17, the ParseIP and ParseCIDR functions now reject IPv4 addresses which contain decimal components with leading zeros.

Ensure that any IP addresses set as environment variables for LOG_CACHE_ADDR, or in other places, do not have leading zeros.

For more information on the context of this change, please refer to the Go 1.17 release notes.

Log Cache CLI 4.0.2

• Plugin is built with Go 1.15.5.
• Go 1.15 contains an important change to the validation of X.509 Certificates that may affect you if the certificate presented by your foundation does not include a Subject Alternative Name. We recommend obtaining a certificate that has the Subject Alternative Name.

Log Cache CLI 4.0.1

• This release intended to bump the plugin to be built with Go 1.15.5 but did not.
• Please upgrade to the v4.0.2 release.

Log Cache CLI 4.0.0

• Deleted apps no longer appear in cf log-meta output by default. To show them, pass --source-type unknown or --source-type all.
• cf log-meta --guid now no longer shows source IDs nor queries Cloud Controller for app names. This speeds up cf log-meta substantially.
• Fixed go mod path by including version in import path, allowing inclusion by other go.mod-using codebases.
• Remove k8s standalone CLI.

Log Cache CLI 3.1.0

Changelog

• cf log-meta --noise now uses a new method for calculating per-source log/metric volume, which should scale to much higher throughput. We encourage those who've tried this tool and given up on its limitations to give it another try.

  Specifically, log/metric volume used to be calculated by streaming logs for each source. Now, the CLI takes a snapshot of Log Cache's /api/v1/meta endpoint endpoint 5 minutes apart, and takes the difference of the two.

Log Cache CLI 2.1.0

Changelog:

• Switched dependency structure to go modules
• Added --name-filter option when tailing metrics against LogCache v2.1.0+
• --type removed in favor of --envelope-class or -c
• --envelope-type given -t short flag

Log Cache CLI 2.0.0

Changelog:

• Allow cf tail --follow to be a long-running process
• Build script no longer specifies GOOS=linux
• Add query subcommand for PromQL endpoints
• Includes cf tail --newline command to replace character with a newline for readability
• Fix bug on cf log-meta --noise subcommand to return correct data
• Works with latest Log Cache API

log cache cli 1.3.0

Changelog:

• Fix capitalization of SourceId and InstanceId to match API
• Add column sorting to log-meta command
• Update help text output