-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(aws-lambda): lazily initialize aws library #11614
Conversation
### Summary Lazily initializes AWS library on a first use, to remove startup delay caused by AWS metadata discovery. Signed-off-by: Aapo Talvensaari <aapo.talvensaari@gmail.com>
fb7a5e3
to
9f4fa97
Compare
Why don't we need a change log? |
Because it is fix over to upcoming unreleased feature THAT already has a changelog, So you can think that there was nothing to fix if this was originally in the original PR. It would be strange if changelog says that we 1) added new feature and 2) fixed it. We can say that we added new feature and be done with it (we didn't fix anything for anyone as nobody is using new feature as it is not released - the audience of changelogs is our users, not us - at least the primary audience). |
### Summary Lazily initializes AWS library on a first use, to remove startup delay caused by AWS metadata discovery. Signed-off-by: Aapo Talvensaari <aapo.talvensaari@gmail.com>
### Summary Lazily initializes AWS library on a first use, to remove startup delay caused by AWS metadata discovery. Signed-off-by: Aapo Talvensaari <aapo.talvensaari@gmail.com>
Summary
Lazily initializes AWS library on a first use, to remove startup delay caused by AWS metadata discovery.
Checklist
CHANGELOG/unreleased/kong
or addingskip-changelog
label on PR if unnecessary. README.md^ this PR does not need any of those, this is on top of unreleased feature.