In pipeline triggers,
inputYaml
parameter is actually a string so the order of elements there matters (service stanza above environment stanza produces different string if those two things were reversed). This a request to document the order of elements expected in that string. Alternatively, treat this as a yaml object where order does not matter. In that case terraform harness provider needs to be adjusted so that it does not produce a diff.