-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Recognize command extensions from plugins and validate CLI input against result commands schema #9171
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #9171 +/- ##
==========================================
+ Coverage 86.93% 87.14% +0.21%
==========================================
Files 302 304 +2
Lines 11368 11462 +94
==========================================
+ Hits 9883 9989 +106
+ Misses 1485 1473 -12
Continue to review full report at Codecov.
|
fd850ea to
11db074
Compare
It ensures that also plugins added externally by invoking `pluginManager.addPlugin` are recognized as external. e.g. such practise can be observed here: https://github.com/serverless/serverless-azure-functions/blob/c53f535204c467339e8ae1f6edb985c3280bc32c/src/index.ts
It's needed to be able to process commands as introduced by plugins without a need of processing Serverless instance
11db074 to
19135d1
Compare
pgrzesik
left a comment
There was a problem hiding this comment.
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 👍
Finalizes 4.0.0 & 5.1.0 from #8364
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)optvariable source (after having all commands schema resolved, last resolution phase was configured to resolve any final properties behindoptsources)