Recognize command extensions from plugins and validate CLI input against result commands schema by medikoo · Pull Request #9171 · serverless/serverless

@medikoo

Finalizes 4.0.0 & 5.1.0 from #8364

  • Parse commands and options as provided via external plugins. For that, needed to move lifecycleEvents configuration 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 opt variable source (after having all commands schema resolved, last resolution phase was configured to resolve any final properties behind opt sources)
  • 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

@medikoo

@codecov

@medikoo

It's needed to be able to process commands as introduced by plugins without a need of processing Serverless instance

@medikoo

@medikoo

@medikoo

@medikoo

@medikoo

pgrzesik

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 medikoo deleted the 0322-recognize-commands-from-plugins branch

March 24, 2021 10:50