Content Discussion: Moving off sam deploy about lamby

[nitsujri]

For me the complexity of managing that service for deploys is not outweighed by the simplicity of systems like GitHub Actions or CircleCI.

100% agreed. Having fully gone through the CodePipeline + CodeBuild, I think in the name of focus + ease of upstart, adding this content section is not in the best interest of the project.

I'll close this for now.

[nitsujri]

Turns out it wasn't so bad, I just needed to follow what other CodeBuild SAM users are doing.

General Steps:

1. sam package output package.yml or any template.yml is spit out as an artifact from the CodeBuild stage.
2. CodePipeline consumes the template and orchestrates CloudFormation to process that file.

Step 2 offloads/acts-as the sam deploy to CloudFormation directly. Now that CodePipeline/CloudFormation is handling the AutoPublishAlias: live I can let it take as long as it needs.

Let me know if there's a section to be had. Happy to help where it makes sense.

[metaskills]

Hey @nitsujri Thanks, I was out the week prior and I'm working thru some old emails. Always appreciate your feedback, some thoughts.

First, let me share that I am not a fan of CodePipeline. For me the complexity of managing that service for deploys is not outweighed by the simplicity of systems like GitHub Actions or CircleCI. That said, I've not yet had the need for an advanced canary deploy option offered by SAM & CodePipeline. If you do, that is fine and why I think a linked blog post from the Lamby site on said topic (or maybe guide) would be helpful. So totally open to doing that.

Second, here is some background on AutoPublishAlias: live as to why it is in the starter and mentioned in that Cold Start issue you linked. I have found that when deploying Rails applications that take a descent amount of traffic that the deploy alias will soften the downstream blow of users hitting that application. This happens even when you do not use provisioned concurrency. In fact, the CI/CD system will finish the sam deploy even before traffic is fully rolled over. Often times it takes a minute or two to switch the alias. When you combine that with how it helps soften rollouts in a clean way with less errors... that's all the deploy method I need.

Again, for me, canaries are kind of moot. We suss out their need in staging. Not to say they are not useful for some and I love the ability. But not the engineering to get there yet because... Code(Deploy|Pipeline) is not super easy. Hence, guide help please.