-
Notifications
You must be signed in to change notification settings - Fork 121
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
PowerShell in Applications Mode #153
Conversation
Initial draft of "PowerShell in Application Mode" specification
…into brucepay_PAM
|
||
This type of PowerShell deployment differs from traditional interactive applications in a number if ways: | ||
- The functionality is likely predefined – the application is composed of a known set of scripts and modules. | ||
- This implies that only a subset of the PowerShell functionality is required. For example, the help and formatting subsystems might be unnecessary. The net result would be faster startup, reduced footprint and consequently a reduced security Surface. |
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.
As for Help System, last days I am trying decouple it to separate dll and module from engine. I believe this is more flexible. Progress is about 80%. There is some problems with internal API problems that can be solved step-by-step PRs. I am ready to push initial PR.
|
||
```JSON | ||
{ | ||
"Action" = "StartPipeline", |
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.
=
is not valid json.
should be
{
"Action": "StartPipeline",
"Pipeline": "get-process | sort -descending | select -first 5"
}
Same for the other JSON examples
I would like to see a full JSON Schema for the proposed input and output. |
@BrucePay let's talk about what you want to do with this one at the next @PowerShell/powershell-committee meeting. |
PowerShell in Applications Mode proposes aset of features to allow a more light-weight PowerShell to be used in scenarios other than the traditional interactive shell.