A couple of times, I’ve gotten snagged by a misspelling or incorrect capitalization of an identifier in a serverless.yml file.
Example: If you put this vpc configuration in your provider block, it will get ignored:
vpc:
SecurityGroupIds:
- sg-xxxxx
SubnetIds:
- subnet-xxxx
Why? Because “SecurityGroupIds” and “SubnetIds” should not have an initial upper-case letter. It’s “securityGroupIds”, etc.
Which is OK, dumb mistake.
But couldn’t serverless issue a warning when the expected fields of ‘vpc’ are not found? or when an object like this ends up being ignored because it’s malformed? Would save a lot of time.