If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
Issue details
After responding to https://github.com/pulumi/pulumi-aws/issues/3632, I thought that my response could (and should) be automated. YAML is all about nesting, and it's pretty common to accidentally mis-nest something. Our documentation doesn't always help there.
code: Cannot assign '{s3Bucket: string, s3Key: string}' to 'archive'
Both s3Bucket and s3Key are valid fields in properties. We could provide a much more helpful error message here:
code: Cannot assign '{s3Bucket: string, s3Key: string}' to 'archive'
Consider moving 's3Bucket: ${s3_bucket_lambda_code.bucket}' up one level to 'properties'
Consider moving 's3Key: helloworld.zip' up one level to 'properties'
Affected area/feature
This feature is restricted to Pulumi YAML's error reporting system.
Hello!
Issue details
After responding to https://github.com/pulumi/pulumi-aws/issues/3632, I thought that my response could (and should) be automated. YAML is all about nesting, and it's pretty common to accidentally mis-nest something. Our documentation doesn't always help there.
Consider this example:
Both
s3Bucket
ands3Key
are valid fields inproperties
. We could provide a much more helpful error message here:Affected area/feature
This feature is restricted to Pulumi YAML's error reporting system.