0

I have a CICD pipeline from a bitbucket repository to a AWS lambda - after push my code gets updated into the lambda in about a minute. Waiting this one minute to fix a small bug, rebuild and push is annoying - but I don't want to get rid off the pipeline.

I can run the buildspec.yaml locally but how should I invoke the built functions. I came up with two ideas:

  1. Localstack
  2. AWS SAM There could also be a third option - which I don't want because it reinvents the wheel
  3. define the lambda event manually and run the my-lambda-code.js manually ()

Regarding 1. self explanatory, I would run my entire CDK project inside localstack and push to the bitbucket repository and expect a slight performance boost. As for 2. how should the workflow look like? I really do want the infrastructure to a be a seperate repository from the codebase of the lambda.

Do you think adding a local deployment in a complex AWS app is essential or overcomplicating.

Improve this question
Related questions
0
Best Practices to deploy serverless app (s3, api gateway, lambda, cognito...) with AWS CDK
1
CICD in AWS - GitHub to Lambda
1
I want to dubug lambda, but cdk synth does not include Lambda Resource, when it is deployed by pipeline stack
Load 6 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.