We didn't define a custom ToJSON for the ParamtersYaml or TagsYaml
objects to generate the more natural key-value style, but we did
define customer instances on the ParameterYaml and TagYaml element
types. This resulted in some weird JSON during generation or capture.
This commit fixes that, relying on the new failing test to be sure.
It has the same values as the separate parent argument, which predated
it. Doing this means that the stackSpec...File functions are only used
in contexts where them being relative makes more more sense.
And then being relative is also required to fix --filter.
Add (failing) spec on StackSpecYaml JSON
Fix invalid FromJSON(Action)
We were loading the same constructor by either tag. I also moved from
asumto(<|>), which produces better failuresFix JSON instance for StackSpecYaml
We didn't define a custom
ToJSONfor theParamtersYamlorTagsYamlobjects to generate the more natural key-value style, but we did define customer instances on theParameterYamlandTagYamlelement types. This resulted in some weird JSON during generation or capture. This commit fixes that, relying on the new failing test to be sure.Update writeStackSpec to use ssSpecRoot
It has the same values as the separate
parentargument, which predated it. Doing this means that thestackSpec...Filefunctions are only used in contexts where them being relative makes more more sense.And then being relative is also required to fix
--filter.Add spec on filtering from the output of generate
This failed until the previous commit.