@Mavi888 this is an awesome tut! Speaking about more complicated setup, I would love to see totorial of setup for a team of developers, where on push to the random branch, we will generate a lambda instance for QA purposes, some kind of stage env (which doesn't affect prod). Another advantage of AWS I think is a good rollback setups, haven't tried it with CDK yet (doing my research now), but with plain pipelines I have an ability to rollback to previous version of a lambdas. That also might be interesting subject to explore. But overall your channel is awesome!
Hi, I am trying to pass environment variables to the CDK stack but they aren't available when the pipeline tries to deploy the stack via CloudFormation. Can someone help me? On my local computer I just stored them in a .env file and accessed them with process.env.XXX but (of course) in the CDK pipeline they aren't available (not in the GH repo). Is there a way to pass those variables to the stack easily?
You're really a great instructor, I started experimenting with CDK watching your videos, can you tell me if it's possible to create the pipeline without the artifact bucket?
@Mavi888 one more thing, as I know we can deploy CDK project into LocalStack, I did tried it, but there were some issues with AWS account I think. This is another suggestion for next tutorial maybe )
You can create 2 pipelines that have 1 stage each and they are attached to the right github branch - stage or prod for example. That will make the result you want.
@@foobar_codes I use the same idea. My problem was that we create a new release branch name for every release version. To solve this, we create a lambda that creates/delete pipeline for the release branch base on the code commit cloud watch event(new release branch created/deleted).
Thanks for the great video and code examples! I have a question for you - How would you go about adding an action to the PreProd stage that would rely on some manual feedback from a user (say a QA person) instead of (or in addition to) the automated ShellScriptAction? Thanks again for the great content, definitely worth subscribing.
Muchas gracias por tus videos, me ha ayudado muchisimo! Ahora estoy teniendo un problema porque ya tengo funcionando mi cdk pipeline con dos stages (source y build) pero no se como almacenar los artifacts en un bucket y tambien necesito agregar un par "manual approve", podrás orientarme? Saludos!!
Thanks @FooBar Serverless ! Is it also possible to create a dynamic short-lived feature branch pipeline automatically? So that when a new branch is pushed to GitHub it creates a new stack for this branch and after 7 days without an update on this branch it should delete this Stack… 🤩
19:07 Yes, please: I want to create a git tag (with a name that includes the timestamp of the latest commit) after successfully deploying to production. (I am using a CodeCommit repo)
Thank you so much for this video, Marcia! I was able to implement CDK Pipelines easily with an existing solution after watching this.
@Mavi888 this is an awesome tut!
Speaking about more complicated setup, I would love to see totorial of setup for a team of developers, where on push to the random branch, we will generate a lambda instance for QA purposes, some kind of stage env (which doesn't affect prod).
Another advantage of AWS I think is a good rollback setups, haven't tried it with CDK yet (doing my research now), but with plain pipelines I have an ability to rollback to previous version of a lambdas. That also might be interesting subject to explore.
But overall your channel is awesome!
You're really a great instructor. I love to watch your tutorials even though I use Python for serverless. Your explanation is much easier to catch!
Thanks a lot 😅
thanks for this :) btw , do you have any content that talks about aws-cdk-lib/pipelines ? the one with self-mutate
struggling with the bootstrap, i put in my account ID and region and paste it in the terminal. I get "Subprocess exited with error 1"
Hi, I am trying to pass environment variables to the CDK stack but they aren't available when the pipeline tries to deploy the stack via CloudFormation. Can someone help me? On my local computer I just stored them in a .env file and accessed them with process.env.XXX but (of course) in the CDK pipeline they aren't available (not in the GH repo). Is there a way to pass those variables to the stack easily?
im going to make a video about this :)
You're really a great instructor, I started experimenting with CDK watching your videos, can you tell me if it's possible to create the pipeline without the artifact bucket?
@Mavi888 one more thing, as I know we can deploy CDK project into LocalStack, I did tried it, but there were some issues with AWS account I think. This is another suggestion for next tutorial maybe )
That's exactly what I was looking for.... thaaaannk youuuu 😍
Yeyyyyy 🎉 🎉 🎉 🎉 🎉
Tanks, great work. Could you provide a pipeline example with git-flow (multibranch strategy)
Noted 📝
You can create 2 pipelines that have 1 stage each and they are attached to the right github branch - stage or prod for example. That will make the result you want.
@@foobar_codes I use the same idea. My problem was that we create a new release branch name for every release version. To solve this, we create a lambda that creates/delete pipeline for the release branch base on the code commit cloud watch event(new release branch created/deleted).
Yes cdk pipelines doesn't support this out of the box to have dynamic branches
really nice video! would love to see a pipeline triggered by GitHub releases instead of push to master
Thanks for the idea!
Thanks for the great video and code examples! I have a question for you - How would you go about adding an action to the PreProd stage that would rely on some manual feedback from a user (say a QA person) instead of (or in addition to) the automated ShellScriptAction? Thanks again for the great content, definitely worth subscribing.
This might help you
stackoverflow.com/questions/64088646/is-there-any-way-to-add-manual-approval-action-to-cdkpipeline
Muchas gracias por tus videos, me ha ayudado muchisimo! Ahora estoy teniendo un problema porque ya tengo funcionando mi cdk pipeline con dos stages (source y build) pero no se como almacenar los artifacts en un bucket y tambien necesito agregar un par "manual approve", podrás orientarme? Saludos!!
lo tengo en cuenta para prox videos de cdk pipeline :)
HOW DO WE DELETE THE STACK WHEN USING CDK PIPELINES?
Thanks @FooBar Serverless ! Is it also possible to create a dynamic short-lived feature branch pipeline automatically?
So that when a new branch is pushed to GitHub it creates a new stack for this branch and after 7 days without an update on this branch it should delete this Stack… 🤩
CDK pipelines don't support this yet :(
hello, I know that you have the sane chanel in spanish, can you give me the link of this content if is possible?
19:07 Yes, please: I want to create a git tag (with a name that includes the timestamp of the latest commit) after successfully deploying to production. (I am using a CodeCommit repo)
Thanks! Would be great if you make something similar with Serverless Framework :)
i dont think serverless framework has support for this :) this is for cdk
Good Work
Thanks
this video help me alot. thanks
Glad to hear that!
It's very great video and I would be more happy if it is in python language, any way thanks
Thank you! :-)
You're welcome!