Repository navigation
[Question] Use AWS SAM on Github pipeline #4963
Description
Hello folks,
I don't know if it the right place to open this discussion but feel free to correct me if something is wrong.
In the pas days I've been working on the development of a CI/CD pipeline using AWS SAM + Github actions.
To maximize build time instead running a single "aws build" and wait all my lambdas been build sequencely I use github actions with matrix strategy to build every resource in parallel. With this solution I can reach my goal. But after that I need to pack and deploy those lambdas. That's where my nightmare begins.
To make things clear:
#build process
sam build resource-id
As every resource is build on it's own container and as output I have the complied code and the template.yml with the correspondent CodeURI replacement I could find a way to merge all builds back on a single template.
Does anyone has a hint ou sugestion for my case ?
PS.: I do not use aws sam build --parallel because to compile as many lambdas I do have on my stack the container does not have enough memory to hadle that. It takes longer to run than runing without the --parallel flag.
Thanks in advance,
Activity
qingchm commentedon Apr 10, 2023
Thanks for reaching out! May I know what's this process like and what's the main paint point right now?
rsorelli-hedgepoint commentedon Apr 18, 2023
The main point is how to build a stack using distribuited containers and after build merge then for a deploy.
Let me try to ilustrate the scenario again:
Each build produces a template.yaml file replacing the "CodeUri" of the lambda pointing to the output artifact of the build
Is there any way I can merge those outputs (template and artifacts) on a thrid container where I can run the "sam deploy" and have both artifacts deployed ?