Increase visibility into New Relic Lambda Layer function changes

[brianwjung]

Summary

Currently, the recommended way to install the New Relic Lambda Layer is to run the New Relic CLI command:

newrelic-lambda layers install --function <function name> --nr-account-id <new relic account ID>

This configures the latest New Relic Lambda Function as a layer to the Lambda function we specified. But we aren't able to see what New Relic Function versions exist and what changes actually occurred between them.

Desired Behaviour

The above is great but ideally, what I would like to also be able to see is a way for us to see all New Relic Lambda Function versions and a changelog of sorts that shows us the changes made whenever a new version is published.

Something that elaborates on what's commited here: https://github.com/newrelic/newrelic-lambda-layers

Possible Solution

Ideally, it would be nice to have it built into the CLI itself as a means of listing New Relic Lambda function versions as well as being able to see relevant changes corresponding to the Lambda function versions.

Alternatively, I'd be okay with even just having the newrelic-lambda-layers repository having some type of mapping that would allow us to see which New Relic Lambda Function maps to a specific release. That would at least give us an idea of whether we're using the latest version and what changes occurred between the version we were using.

Additional context

This would allow people to know exactly what they're updating to and for. Additionally, this would make it so we wouldn't have to guess on which version to use, why we should use it, and whether a version even still exists.

[kolanos]

@brianwjung These are all good suggestions. We do maintain a change log of sorts for the layers themselves here: https://github.com/newrelic/newrelic-lambda-layers/releases/ but these releases are not currently mapped to their respective layer ARN versions. We also have a site to display the current latest versions by runtime and region here: https://layers.newrelic-external.com/, but again, this ionly gets at part of the problem you've identified.

[jmm]

FWIW, unless I've missed something or something has changed since I last checked, GitHub Releases are a terrible substitute for a change log, because they're not readily searchable or scannable (and I believe they're not readily portable outside of GitHub either).