Livecoding deployment pipelines using Go and dagger.io

[@mohamedimranechehabi5735]

THE CHOSEN ONE IS BACK!

[@ixueyi]

Glad you are back👏

[@mateoleoncamacho3222]

I love your videos, you do have some great teaching skills. Please keep it up.

[@arnabthakuria2243]

Thank you so much for creaing content like this. Please do not stop

[@mowazzemhosen366]

at last you are back.

[@ogogoleg]

Thank you! It's nice again to hear your little jokes "to myself"!

[@grizzle8911]

In a terminal, use ctrl+l (lower case L) - it will change your life ;) - its the same as typing "clear"

[@kubakluzniak4744]

Hey , could you do video about your development setup ( nvim etc) ?

[@NicJackson]

I have been asked to do this a few times. I think it is a good idea. I have been mostly using the same setup now for about 10 years and it is working well for me.

[@npradeeptha]

I would love to see how you handle credentials. For example if you use Vault, the CI systems have role based auth to Vault whereas in local it would use user/pass to log in.

[@NicJackson]

This is a great shout out, abstraction between environments is super important. I was actually thinking how I do this today with the example for the source code. The example on dagger.io has a great example that uses the built in Git repo capability. I was using local source as I did not yet have a repo but in the next session I am going to expand that to allow both depending on where you run things.

[@npradeeptha]

@@NicJackson That would be great! It would also be nice to see how you abstract some of the functionality into their own pkgs instead of using a single go file.

[@NicJackson]

@@npradeeptha Yes, I am going to try and tackle this too, just need to figure it out myself first :)

[@alfi7135]

Hello there Hope you're doing well

[@adrien-barret]

Cd is also the others things coming with it, if I take argocd it will make your deployment consistant where this kind of tech doesn’t. :p

[@NicJackson]

A tool does not give you consistency, process and discipline are the things that give consistency. It is possible to create an inconsistent mess no matter which tool you use. You also need to consider the use case beyond Kubernetes, while popular it is not used by everyone, or folks are using Kubernetes and something else. In the latter case something like Dagger could actually help you with a consistent approach, Argo becomes a runner, the pipeline is defined in a universal tool like dagger. This same pipeline could run on many different systems, Circle, Github Actions, Azure pipelines. This is what I like about tools like dagger, it gives you an abstraction which makes changing platforms easier. Yes you need to depend on Dagger but we do that on Docker containers and that has not proven a bad choice so far. Dagger is not CD, you are 100% right this is way more than a just the pipeline, Dagger is only a way of describing pipelines as code.

[@adrien-barret]

@@NicJackson I totally agree with you. It's just that different eng I follow explain how to use like ci/cd, pulumi, etc and people follow that. what I see after is a bunch of security issues or missing tests, etc... I think it's just borring me to see my reddit/discords with all the same questions on it is not working or they was hacked, etc exept what they just learned in the xyz video ;)