(Docs) Added information on the deployment docs for reducing deployment size when using aws/google SDKs #1683
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…reducing deployment size when using aws/google dependencies
Member
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My codebase was sitting just on the edge of maximum deployment size & every now and then staging deployments would complain after our patching routine because google or AWS added new services that increased the deployment size.
Our solution have for years been just to extend the never ending exclude list with new services. But this time i got quite annoying by it and with a few searches i found some nifty composer scripts that can be used to automatically cleanup unused services in both the Google and AWS SDKs!
AWS SDK was heavily inspired by aws/aws-sdk-php#2456 - so the syntax is much the same.
This change adds a small callout segment in the deployment which just highlights this as these packages are often found in serverless deployments.