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: clu-getstart.md
+5-4Lines changed: 5 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,7 @@ To test on osx/linux boxes, do #1, open `<repo-root>\drop\clurun`, copy the flav
63
63
(All of those are subject to change, contact yugangw or adxsdkdev for any questions)
64
64
65
65
### Quick introductions on cmdlets
66
-
* Run commands using the ‘az’ prefix, cmdlet nouns, and cmdlet verbs, for example, `az environment get` maps to the cmdlet `Get-AzureRmEnvironment`
66
+
* Run commands using the ‘az’ prefix, cmdlet nouns, and cmdlet verbs, for example, `az env get` maps to the cmdlet `Get-AzureRmEnvironment`
67
67
* Cmdlet parameters use the double dash (--) so for example, getting a subscription with a particular name would be: `az subscription get –-SubscriptionName “name of subscription"`
68
68
* To log in, 3 options
69
69
* login interactively using device flow, this is the only option for msa account or any org-id with 2fa enforced, example: `az account add`
@@ -73,14 +73,14 @@ To test on osx/linux boxes, do #1, open `<repo-root>\drop\clurun`, copy the flav
73
73
```az subscription get --SubscriptionName | az context set```
74
74
* You can capture piped output using redirection to a file - the result will be the json serialization of the output object.
75
75
```az subscription get > subscriptions.json```
76
-
* You can use file input tu aparameter using '@' notation:
76
+
* You can use file input to a parameter using '@' notation:
77
77
```az command --param1 @file1.json```
78
78
Reads input from file1.json and attempts to deserialize the .net object that is the Parameter type for ```param1```
79
79
```az command --param1 @@file1.json```
80
80
Does the same thing, but treats the input from ```file1.json``` as if it come from the pipeline, so that multiple objects will result in multiple invocations of ```ProcessRecord()``` for the target cmdlet.
81
81
* There are some known issues with the current approach to sessions, which can cause session variables to not be propagated when running cmdlets in a pipeline, to work around this, set the 'CmdletSessionId' environment variable to a numeric value - all cmdlets running from the shell will use that session id, and sessions will work with pipelining
82
82
83
-
```set CmdletSessionId=1010 ```
83
+
```set AzureProfile=1010 ```
84
84
85
85
### Testing Cmdlets
86
86
@@ -119,7 +119,8 @@ Please set the environment variables for either Username/Password (no 2FA) or Se
119
119
120
120
- To implement an xunit bash scenario test you must
121
121
- Add a ```[Collection("SampleCollection")]``` attribute to your test class
122
-
- Add a field to your class of type ```ScenarioTestFixture``` and add a constructor that initializes it
122
+
- Add a field to your class of type ```ScenarioTestFixture``` and add a constructor that initializes it.
0 commit comments