Invalid fields on subresources can output confusing errors

[beam-sysuser]

In this example the CloudFrontOriginResource takes a domain-name not a domain. The error is hard to parse because it's not the usual "invalid field" error.

$ gyro up lower/uat.gyro 
↓ Loading plugin: gyro:gyro-aws-provider:0.99.0-SNAPSHOT
↓ Loading plugin: gyro:gyro-ssh-plugin:0.99.0-SNAPSHOT
⟳ Refreshed resources: 25
Error: Can't set origin to [{id=Custom-origin.uat.gyro.psdops.com, domain=origin.uat.gyro.psdops.com, custom-origin=[{http-port=80, origin-keep-alive-timeout=5, origin-read-timeout=30, origin-protocol-policy=http-only}]}] because it can't be converted to an instance of java.util.Set<gyro.aws.cloudfront.CloudFrontOrigin>!
In lower/uat.gyro from line 128 at column 5 to line 138 at column 7:

128:     origin

129: id: "Custom-origin.uat.$(project).psdops.com"

130: domain: "origin.uat.$(project).psdops.com"

131:

132: custom-origin

133:     http-port: 80

134:     origin-keep-alive-timeout: 5

135:     origin-read-timeout: 30

136:     origin-protocol-policy: 'http-only'

137: end

138:     end

[GYRO-393] created by beetlebugorg