-
Notifications
You must be signed in to change notification settings - Fork 402
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
docs(install): add amplify-cli instructions for public layer #754
docs(install): add amplify-cli instructions for public layer #754
Conversation
Thanks a lot for your first contribution! Please check out our contributing guidelines and don't hesitate to ask whatever you need. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps worth adding a link to find the latest Lambda Layer since that will change over time?
Nvm I'm drunk. I immediately thought this was for the Amplify CLI docs :D |
Awesome work, congrats on your first merged pull request and thank you for helping improve everyone's experience! |
…tools-python into develop * 'develop' of https://github.com/awslabs/aws-lambda-powertools-python: chore(deps-dev): bump mkdocs-material from 7.3.2 to 7.3.3 (aws-powertools#758) chore(deps-dev): bump flake8-comprehensions from 3.6.1 to 3.7.0 (aws-powertools#759) chore(deps): bump boto3 from 1.18.58 to 1.18.59 (aws-powertools#760) chore(deps-dev): bump coverage from 6.0 to 6.0.1 (aws-powertools#751) chore(deps): bump boto3 from 1.18.56 to 1.18.58 (aws-powertools#755) docs: add amplify-cli instructions for public layer (aws-powertools#754) Signed-off-by: heitorlessa <[email protected]>
Description of changes:
After discussing with Alex and Heitor on this tweet and in DMs I've added a section on how to add
aws-lambda-powertools-python
in an existing Amplify project.Just documentation changes
Checklist
View rendered docs/index.md