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
+13-13Lines changed: 13 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ CLUPackages require some additional files to direct generation of indexing, and
25
25
| ------------- |:-------------:|
26
26
| CommandAssemblies | File name of cmdlets assembly(ies) |
27
27
| NounPrefix | ‘AzureRm’ The part of the cmdlet noun to remove in clu commands|
28
-
| NounFirst | if true, the verb comes at the end of the command (e.g. azure resource get)|
28
+
| NounFirst | if true, the verb comes at the end of the command (e.g. az resource get)|
29
29
30
30
*\<modulename\>.nuspec.template, which contains nuspec format metadata about the package – the base temaplate is in tools\clu\Microsoft.Azure.Commands.nuspec.template. Here are the special fields defined in this template:
31
31
* %PackageId% - replace with the module name (Microsoft.Azure.Commands.\<rp-name\>)
@@ -52,31 +52,31 @@ CLUPackages require some additional files to direct generation of indexing, and
52
52
1. Run `<repo-root>\tools\CLU\BuildAndInstallClu.bat` which build and generate all cmdlet packages and deploy to under `<repo root>\drop\clurun` folder, with 3 flavors `win7-x64`, `osx.10.10-x64` and `ubuntu.14.04-x64`. When you have a clean environment or just pull from upstream, you should clean temporary bits such as `git clean -xdf`, and run this command.
53
53
2. Run `<repo-root>\tools\CLU\BuildCmdlet <package name like Microsoft.Azure.Commands.Profile>` <namelike:Microsoft.Azure.Commands.Profile>", this will build and refresh an individual cmdlet package.
54
54
55
-
After #1 above is finished, you can run `drop\clurun\<platform>\azure.bat help` to explore.
55
+
After #1 above is finished, you can run `drop\clurun\<platform>\az.bat help` to explore.
56
56
57
57
To debug, set environment variable of `DebugCLU` to "1". Then on running any command, you will be prompted to attach a debugger.
58
58
59
-
There is also `<repo-root>\tools\CLU\SetupEnv.bat` which is a windows batch wrapping around the `BuildAndInstallClu.bat`, plus set the `DebugCLU` for you, and add the `drop\clurun\win7-x64\azure.bat` to the PATH environment variable.
59
+
There is also `<repo-root>\tools\CLU\SetupEnv.bat` which is a windows batch wrapping around the `BuildAndInstallClu.bat`, plus set the `DebugCLU` for you, and add the `drop\clurun\win7-x64\az.bat` to the PATH environment variable.
60
60
61
-
To test on osx/linux boxes, do #1, open `<repo-root>\drop\clurun`, copy the flavor folder to your target machine, and run the "azure.sh" inside. Make sure set execution permission using `chmod +x azure.sh clurun`
61
+
To test on osx/linux boxes, do #1, open `<repo-root>\drop\clurun`, copy the flavor folder to your target machine, and run the "az.sh" inside. Make sure set execution permission using `chmod +x az.sh clurun`
62
62
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 ‘azure’ prefix, cmdlet nouns, and cmdlet verbs, for example, `azure environment get` maps to the cmdlet `Get-AzureRmEnvironment`
67
-
* Cmdlet parameters use the double dash (--) so for example, getting a subscription with a particular name would be: `azure subscription get –-SubscriptionName “name of subscription"`
66
+
* Run commands using the ‘az’ prefix, cmdlet nouns, and cmdlet verbs, for example, `az environment get` maps to the cmdlet `Get-AzureRmEnvironment`
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
-
* login interactively using device flow, this is the only option for msa account or any org-id with 2fa enforced, example: `azure account add`
70
-
* login with user and password, this works on org-id w/o 2fa enforced, example: `azure account add --Username [email protected] --Password password1`
71
-
* login as service principal. Example: `azure account add --ServicePrincipal --TenantId <tenant> --ApplicationId <id> --Secret <secret>`
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`
70
+
* login with user and password, this works on org-id w/o 2fa enforced, example: `az account add --Username [email protected] --Password password1`
71
+
* login as service principal. Example: `az account add --ServicePrincipal --TenantId <tenant> --ApplicationId <id> --Secret <secret>`
72
72
* Piping between cmdlets should work the same way that Powerhell piping works
73
-
```azure subscription get --SubscriptionName | azure context set```
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
-
```azure subscription get > subscriptions.json```
75
+
```az subscription get > subscriptions.json```
76
76
* You can use file input tu aparameter using '@' notation:
77
-
```azure command --param1 @file1.json```
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
-
```azure command --param1 @@file1.json```
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
Copy file name to clipboardExpand all lines: examples/resource-management/03-Deployments.sh
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -3,14 +3,14 @@ set -e
3
3
printf"\n=== Provisioning Deployments in Azure ===\n"
4
4
5
5
printf"\n1. Creating a new resource group: %s and location: %s.\n""$groupName""$location"
6
-
azure group create --name "$groupName" --location "$location"
6
+
az group create --name "$groupName" --location "$location"
7
7
8
8
printf"\n2. Test template with dynamic parameters\n"
9
-
azure group deployment test -g "$groupName" --templatefile $BASEDIR/sampleTemplate.json --siteName "$resourceName" --hostingPlanName "$resourceName" --siteLocation "$location" --workerSize "0"
9
+
az group deployment test -g "$groupName" --templatefile $BASEDIR/sampleTemplate.json --siteName "$resourceName" --hostingPlanName "$resourceName" --siteLocation "$location" --workerSize "0"
10
10
11
11
printf"\n3. Test template with JSON parameter object\n"
12
-
azure group deployment test -g "$groupName" --templatefile $BASEDIR/sampleTemplate.json --templateparameterobject "{\"siteName\":\"$resourceName\",\"hostingPlanName\":\"$resourceName\",\"siteLocation\":\"$location\",\"workerSize\": 0 }"
12
+
az group deployment test -g "$groupName" --templatefile $BASEDIR/sampleTemplate.json --templateparameterobject "{\"siteName\":\"$resourceName\",\"hostingPlanName\":\"$resourceName\",\"siteLocation\":\"$location\",\"workerSize\": 0 }"
0 commit comments