You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ It is important to note, that despite the use-case described below for this proj
8
8
*[Example](#example)
9
9
*[Security](#security)
10
10
11
-
###Origin <aid="Origin"></a>
11
+
###<aid="Origin"></a> Origin
12
12
13
13
This project originated out of the need to execute various Powershell commands (at fairly high volume and frequency) against services within Office365/Azure bridged via a custom node.js implemented REST API; this was due to the lack of certain features in the REST GraphAPI for Azure/o365, that are available only in Powershell.
14
14
@@ -22,7 +22,7 @@ The diagram below should conceptually give you an idea of what this module does.
22
22
23
23

24
24
25
-
###Usage <aid="usage"></a>
25
+
###<aid="usage"></a> Usage
26
26
27
27
To use StatefulProcessCommandProxy the constructor takes one parameter which is a configuration object who's properties are described below. Please refer to the example (following) and the unit-test for more details.
28
28
@@ -82,7 +82,7 @@ To use StatefulProcessCommandProxy the constructor takes one parameter which is
82
82
83
83
Its highly recommended you check out the unit-tests for some examples in addition to the below:
84
84
85
-
###Example <aid="example"></a>
85
+
###<aid="example"></a> Example
86
86
87
87
Note this example is for a machine w/ bash in the typical location. Windows (or other) can adjust the below as necessary to run).
88
88
@@ -162,7 +162,7 @@ setTimeout(function() {
162
162
163
163
```
164
164
165
-
###Security <aid="security"></a>
165
+
###<aid="security"></a> Security
166
166
167
167
Obviously this module can expose you to some insecure situations depending on how you use it... you are providing a gateway to an external process via Node on your host os! (likely a shell in most use-cases). Here are some tips; ultimately its your responsibility to secure your system.
0 commit comments