Recognize command extensions from plugins and validate CLI input against result commands schema by medikoo · Pull Request #9171 · serverless/serverless
Finalizes 4.0.0 & 5.1.0 from #8364
- Parse commands and options as provided via external plugins. For that, needed to move
lifecycleEventsconfiguration to config schema, as it's crucial in detecting which AWS provider commands were adapted in context of other provider (note in such cases other provider doesn't have to configure command explicitly, it's enough that it attaches some function to pre-configured command lifecycle events) - Finalize resolution of
optvariable source (after having all commands schema resolved, last resolution phase was configured to resolve any final properties behindoptsources) - Having all commands data, validate unrecognized command in context of main script. Additionally validate unrecognized options, signalling that with next major such usage will throw
- Maintenance improvements to main process file
It's needed to be able to process commands as introduced by plugins without a need of processing Serverless instance
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good - nothing to add 👍
medikoo
deleted the
0322-recognize-commands-from-plugins
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters