Skip to content

Remove config validation warnings: "unrecognized property 'module'" #575

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

Closed
wants to merge 1 commit into from

Conversation

DarrenStack
Copy link

@DarrenStack DarrenStack commented Dec 11, 2020

Also brought up here: serverless/serverless#8423

Function Schema Validation is executed by default with the update from Serverless to 2.7.0. This picks up validation errors for the "module" keyword which is used in this plugin.

In Serverless 2.10.0, they introduced the "defineFunctionProperties" function serverless/serverless#8462 This can be used to extend the aws function definition to include new keywords.

I believe adding the following code to the constructer of the plugin would eliminate these warnings but it would cause errors with anyone using a version of Serverless before 2.10.0.

@hadi-alnehlawi
Copy link

Have you guys managed to resolve the issue other than updating manually:
serverless-python-requirements -> index.js

@medikoo
Copy link
Contributor

medikoo commented Aug 17, 2021

@DarrenStack can you update against master? Having that we will be able to merge this

@rileypriddle
Copy link
Contributor

what is required to get this merged into master?

@pgrzesik
Copy link
Contributor

@rileypriddle There are failing tests - it should be rebased on top of current master branch, additionally, it should be good to introduce a change where the schema is applied only if the functionality for adding it is exposed by the Framework so we will avoid breaking it for older versions of the Framework. Would you be interested in tackling that?

@pgrzesik
Copy link
Contributor

Closing in favor of: #641

@pgrzesik pgrzesik closed this Nov 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants