Skip to content

Add ConfigSchema to satisfy schema validation in Serverless 1.79.0 #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 22, 2020

Conversation

jeffwasher
Copy link

I just upgraded my serverless cli to 1.79.0 and started seeing this warning when deploying:

Serverless: Configuration warning at 'functions.myLambdaFunction.events[0]': unsupported function event
Serverless:  
Serverless: If you prefer to not continue ensure "configValidationMode: error" in your config
Serverless: If errors are influenced by an external plugin, enquiry at plugin repository so schema extensions are added (https://www.serverless.com/framework/docs/providers/aws/guide/plugins#extending-validation-schema)
Serverless: If errors seem invalid, please report at https://github.com/serverless/serverless/issues/new?template=bug_report.md
Serverless: If you find this functionality problematic, you may turn it off with "configValidationMode: off" setting

This PR just defines the schema for custom properties and the preExistingCloudFront function event as per https://www.serverless.com/framework/docs/providers/aws/guide/plugins/#extending-validation-schema.

Copy link
Contributor

@horike37 horike37 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jeffwasher
Thanks! This is great. more safety 👍

@horike37 horike37 merged commit 240c509 into serverless-operations:master Aug 22, 2020
@horike37
Copy link
Contributor

🎉 This PR is included in version 1.1.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants