See #14 . My research suggests that there isn't a perfect, no-default-in-template, ignore-when-not-set solution for CloudFormation Integer types.
Two possible fixes:
Set them to Default: -1 then ignore that via a modified condition, which is what this PR does.
Change to String type, perhaps with some integer-like regex validation.
Template looks a little strange on-render, as text says the defaults for these are 20/10, which they are when-absent in the launched image, and the env will be absent if these are left as -1 per the template default, it's just a little odd-looking, but works.
With this change you can again click-through template to launch, without being forced to fill-in the defaults for these two parameters, which avoids setting the env for them in the container-launch, which also avoids missing a change in defaults there.
See #14 . My research suggests that there isn't a perfect, no-default-in-template, ignore-when-not-set solution for CloudFormation
Integertypes.Two possible fixes:
Default: -1then ignore that via a modified condition, which is what this PR does.Stringtype, perhaps with some integer-like regex validation.Template looks a little strange on-render, as text says the defaults for these are 20/10, which they are when-absent in the launched image, and the env will be absent if these are left as
-1per the template default, it's just a little odd-looking, but works.With this change you can again click-through template to launch, without being forced to fill-in the defaults for these two parameters, which avoids setting the env for them in the container-launch, which also avoids missing a change in defaults there.
Fixes #14.