Repository navigation
feat(commons): add Lambda Metadata Service support - #5106
Conversation
|
|
You could've attributed the commits to me since I was the original author. |
|
Sorry, the original PR was mashed up with a bunch of other stuff and I ended up copying and pasting the stuff into a new branch on my local machine and didn't think because we were in such a rush to get it merged. |
|
That said, this is one of the last commits we merged so if we act quickly we could still have a chance to change the author if we temporarily allow a force push to Edit: Actually, a revert is probably better because the rebase will change the commit hashes of of the commits ahead of this. Happy to do it but we need to be quick because ideally we would have released this yesterday. |
|
All good now, reverted and recreated the PR with the correct attribution. |
|
Thanks - appreciate it |



Summary
Changes
The PR adds a new
getMetadata()utility function under thecommonspackage that allows customers to fetch metadata from the Lambda Metadata Endpoint. As of now, only theAvailabilityZoneIdfield is present. The utility automatically detects when not running in a Lambda environment and returns an empty response, this eases testing and local development.The PR also adds a new doc page and two code snippets for the feature.
Issue number: closes #5105
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.