Skip to content
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

Use chalice deploy to only update lambda #2018

Open
nishant-emburse opened this issue Feb 10, 2023 · 1 comment
Open

Use chalice deploy to only update lambda #2018

nishant-emburse opened this issue Feb 10, 2023 · 1 comment

Comments

@nishant-emburse
Copy link

nishant-emburse commented Feb 10, 2023

Is there a way to use chalice deploy to only update a lambda function?

Currently, I have an existing API Gateway that has several routes defined. Each of these routes point to a different lambda function. E.g.,:

APIGateway X
│
└───/endpoint1 --> Points to lambda1
│   
└───/endpoint2--> Points to lambda2
....
│   
└───/endpoint<n> --> Points to lambda<n>

The creation of resources (APIG and Lambdas) is handled via Terraform and the deployment of lambdas is being handled by a legacy CI system using aws --profile <profile> lambda update-function-code --function-name <name> --zip-file <file> --publish command. Not all of this lambdas live in the same repository and its not possible to house them together at this point. But I want to move away from this system and exploring the possibility of using chalice's deployment capabilities. The problem is I can't change the existing architecture since that's a huge lift.

So essentially I want to only update the lambda code using chalice and not touch any other resources. Is this possible to do? I went over #604 but didn't find a viable solution.

@tareshss
Copy link

tareshss commented Aug 9, 2023

The only way I have found to do something similar but not exact is to split my project into a microservice setup using Blueprints and multiple chalice projects under one repo. where i only deploy the microservice that i am working on while not needing to deploy other microservice.

For example you can have a one chalice project microservice that handles user accounts (e.g user CRUD operations), which would be different from your business/feature chalice project microservices.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants