Skip to content
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

Generalize command service functionality away from powershell only #4

Open
bitsofinfo opened this issue Feb 18, 2015 · 2 comments
Open

Comments

@bitsofinfo
Copy link
Owner

There are several things that can be done to make this more of a generic "shell agnostic" wrapper around stateless-process-command-proxy

  1. Support configurable function in constructor to handle argument sanitization
  2. Support configurable function in constructor to permit modifcation of all arguments, i.e. for PS commands the PSCommandService auto prepends a "-" to all argument names
  3. Rename to CommandService, get rid of PS
@gkhatib
Copy link

gkhatib commented Mar 26, 2015

Can this be used to run Powershell scripts, or is it just for commands ? Thanks.

@bitsofinfo
Copy link
Owner Author

Sure, but I suggest you just use https://github.com/bitsofinfo/stateful-process-command-proxy instead (the lower level module). Create your custom powershell script then invoke it via that. This project (powershell-command-executor) is for a registry of pre-defined commands, see the README for details.

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

No branches or pull requests

2 participants