Re:Forget CDK and AWS's insane costs. Pulumi and DigitalOcea...
by kevincox on Thursday November 07, 2024 @01:53PM
(#42079645)
And it breaks every time a variable gets a `:` inside of it and now you are producing invalid yaml everywhere you forgot to call `| toYaml`.
Re:Forget CDK and AWS's insane costs. Pulumi and DigitalOcea...
by smw on Thursday November 07, 2024 @06:28PM
(#42082326)
Never read anything more true in my life!
Re:Forget CDK and AWS's insane costs. Pulumi and DigitalOcea...
by adhamsalama on Friday November 08, 2024 @04:52PM
(#42090754)
I once got a nil pointer exception when I updated a helm chart. I wondered why the hell am I getting a nil pointer exception for updating a YAML file. After some investigation I found an issue on GitHub where the maintainers said the Go team says this is an intended behavior for some case in Go templates.
Wasn't fun.
Re:Forget CDK and AWS's insane costs. Pulumi and DigitalOcea...
by benatkin on Friday November 08, 2024 @08:32PM
(#42091895)
That isn't a typical nill/null exception, like in JavaScript, ruby, and python. That's in a language where a lot of values are non-nullable, and some of the ones that are have zero-values that can be used without getting a nil pointer exception. https://go.dev/tour/moretypes/12
So, there's a good chance was an error that was really unexpected and it's better to show the error than to risk producing bad output.
Every time I see " | nindent whatever" I'm asking why the fuck the tool cannot manage indentation.