-
Notifications
You must be signed in to change notification settings - Fork 225
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
added cli option to preserve VPC settings on update; fixes #78 #116
Conversation
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.
In the deploy method while calling the update_function preserver_vpc kwargs needs to be assigned with preserve_vpc. Currently it is passed to use_s3 param as True
aws_lambda/aws_lambda.py
Outdated
@@ -111,14 +112,15 @@ def deploy( | |||
|
|||
existing_config = get_function_config(cfg) | |||
if existing_config: | |||
update_function(cfg, path_to_zip_file, existing_config) | |||
update_function(cfg, path_to_zip_file, existing_config, preserve_vpc) |
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.
Needs to pass preserve_vpc value as kwargs.
Alright I've made that change to call it using kwargs. Anything else? What is the procedure for getting PRs merged and new releases built? |
@nficano is this repo still maintained? Do you have a procedure for merging PRs and getting new releases built? |
This adds a command line option called
--preserve-vpc
which allows you to omit the VPC settings (i.e. subnets and security groups) so that it will preserve whatever settings are already present on updates. This is useful when deploying the same function to multiple accounts where the security groups and subnets will necessarily change.