optional obviates lookup(..., null) calls for objects
lookup(o, k) without a default is deprecated in favor of o[k] or direct attr access (o.k)
log_configuration, repository_credentials, and system_controls had needlessly opaque any types which hinder DX and make subtle bugs more likely (e.g. in the types of log_configuration.options values)
since all attributes of container_definition are now typed there's no reason not to type it as well
following the AWS documentation's field order makes types easier to verify for completeness & correctness
what
log_configuration
,repository_credentials
,system_controls
,container_definition
jsonencode
/jsondecode
cyclewhy
optional
obviateslookup(..., null)
calls for objectslookup(o, k)
without adefault
is deprecated in favor ofo[k]
or direct attr access (o.k
)log_configuration
,repository_credentials
, andsystem_controls
had needlessly opaqueany
types which hinder DX and make subtle bugs more likely (e.g. in the types oflog_configuration.options
values)container_definition
are now typed there's no reason not to type it as welllog_configuration
appropriately obviates explicittostring
&null
handling; resolves #151for
-expressions iterate over maps & objects by key in lexicographic orderjsonencode
-ing the final container definition only tojsondecode
forjson_map_object
is redundantRefs
154