-
Notifications
You must be signed in to change notification settings - Fork 163
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
increasing default lambda memory size #518
Conversation
@@ -5,7 +5,7 @@ ipdb>=0.12 | |||
# testing tools | |||
pylint>=2.3.1 | |||
coverage>=4.5.4 | |||
pytest>=5.3.5 | |||
pytest>=6.0.0 |
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.
@ammokhov We have to manually apply this config to existing CFN RPs correct? If so, is there a better way that CFN RP developers could get notified about these types of changes? cc: @jotompki |
we dont, it's a common package and if other prs do not have merge conflicts then you can just restart travis job |
@ammokhov Sorry, I did not understand your response, let me re-ask my question... There was a similar template change (rpdk protocol upgrade, if i remember correctly) where the new template was not applied to existing CFN RP flies that end-users made with cfn-cli (ie. I am asking if this template change will similarly need to be manually applied to end-user CFN RPs files or if the |
Sorry, ignore previous reply I misunderstood your question. |
Issue #, if available: #510
Description of changes:
increasing the default memory size
bumping pytest to 6.x as annotations were not recognized as callable pytest-dev/pytest#7473
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.