Zero values vs null values about goformation HOT 8 CLOSED

I've hit the same problem with the "Essential" property of a container definition. Is there a suggested solution? I'm happy to implement a workaround if you point me how we should resolve this issue.
Shouldn't these kind of fields be pointers? That way it should work as users expect.

from goformation.

@deoxxa @neoandroid Can we probably close this as resolved, as @majasb has contributed fixes for booleans and numbers in #133?

from goformation.

Having similar problem:

			Monitoring: &cloudformation.AWSEC2LaunchTemplate_Monitoring{
				Enabled: false,
			},

is rendered as following in yaml output

        Monitoring: {}

from goformation.

I've had the same issue with the AWSLogsSubscriptionFilter type. It has a parameter named FilterPattern. In order to catch all events, you simply supply an empty string.

However, due to empty string being a null string in Go, the value is not included in the generated template.

from goformation.

ECS ContainerDefinition Essential attribute is not required and of type boolean, but then omitempty prevent to set value to false. Issue with that is that the actual API default is true : "If this parameter is omitted, a container is assumed to be essential.".
So there's no way to declare a non-essential containerdefinition

from goformation.

I think it's clear this library needs to transition to using pointers instead of values. It's causing a ton of rough edges. Unfortunately it may be a while before I have time to implement it, however if anyone else wants to have a go in the meantime i'll happily accept a PR.

from goformation.

@rubenfonseca if I am correct this would be solved in v6 looking on behaviour of my issue - #474

from goformation.

That's right! Thank you for pointing this our @xrn.

from goformation.