Skip to content

feat(commons): add Lambda Metadata Service support - #5106

Merged
svozza merged 3 commits into
mainfrom
lambda-metadata-service
Mar 18, 2026
Merged

svozza merged 3 commits into
mainfrom
lambda-metadata-service

Conversation

@svozza

@svozza svozza commented Mar 18, 2026

Copy link
Copy Markdown
Contributor

Summary

Changes

The PR adds a new getMetadata() utility function under the commons package that allows customers to fetch metadata from the Lambda Metadata Endpoint. As of now, only the AvailabilityZoneId field 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.

@svozza
svozza requested a review from sdangol March 18, 2026 15:34
@svozza svozza self-assigned this Mar 18, 2026
@pull-request-size pull-request-size Bot added the size/L PRs between 100-499 LOC label Mar 18, 2026
@svozza
svozza merged commit bdfa583 into main Mar 18, 2026
49 checks passed
@svozza
svozza deleted the lambda-metadata-service branch March 18, 2026 20:42
@dreamorosi

Copy link
Copy Markdown
Contributor

You could've attributed the commits to me since I was the original author.

@svozza

svozza commented Mar 19, 2026

Copy link
Copy Markdown
Contributor 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.

@svozza

svozza commented Mar 19, 2026 •

Copy link
Copy Markdown
Contributor Author

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 main to change it.

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.

@svozza

svozza commented Mar 19, 2026

Copy link
Copy Markdown
Contributor Author

All good now, reverted and recreated the PR with the correct attribution.

@dreamorosi

Copy link
Copy Markdown
Contributor

Thanks - appreciate it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/L PRs between 100-499 LOC

3 participants