Merge pull request #104804 from v-thepet/azure-cli

Change code blocks to shell for sfctl

Author: PRMerger6

articles/service-fabric/service-fabric-application-lifecycle-sfctl.md

@@ -43,7 +43,7 @@ Before you create an application, upload the application package to the Service
 For example, if your application package is in the `app_package_dir` directory, use the following commands to upload
 the directory:
 
-```azurecli
+```shell
 sfctl application upload --path ~/app_package_dir
 ```
 
@@ -53,7 +53,7 @@ For large application packages, you can specify the `--show-progress` option to
 
 When the upload is finished, provision the application. To provision the application, use the following command:
 
-```azurecli
+```shell
 sfctl application provision --application-type-build-path app_package_dir
 ```
 
@@ -65,7 +65,7 @@ It's recommended that you remove the application package after the application i
 
 To delete the application package from the image store, use the following command:
 
-```azurecli
+```shell
 sfctl store delete --content-path app_package_dir
 ```
 
@@ -75,7 +75,7 @@ sfctl store delete --content-path app_package_dir
 
 After you provision the application, use the following command to name and create your application:
 
-```azurecli
+```shell
 sfctl application create --app-name fabric:/TestApp --app-type TestAppType --app-version 1.0
 ```
 
@@ -90,7 +90,7 @@ After you have created an application, create services from the application. In
 stateless service from our application. The services that you can create from an application are defined in a service
 manifest in the previously provisioned application package.
 
-```azurecli
+```shell
 sfctl service create --app-id TestApp --name fabric:/TestApp/TestSvc --service-type TestServiceType \
 --stateless --instance-count 1 --singleton-scheme
 ```
@@ -99,15 +99,15 @@ sfctl service create --app-id TestApp --name fabric:/TestApp/TestSvc --service-t
 
 To verify everything is healthy, use the following health commands:
 
-```azurecli
+```shell
 sfctl application list
 sfctl service list --application-id TestApp
 ```
 
 To verify that the service is healthy, use similar commands to retrieve the health of both the service and the
 application:
 
-```azurecli
+```shell
 sfctl application health --application-id TestApp
 sfctl service health --service-id TestApp/TestSvc
 ```
@@ -122,7 +122,7 @@ To remove an application, complete the following tasks:
 
 To delete the application, use the following command:
 
-```azurecli
+```shell
 sfctl application delete --application-id TestEdApp
 ```
 
@@ -131,7 +131,7 @@ sfctl application delete --application-id TestEdApp
 After you delete the application, you can unprovision the application type if you no longer need it. To unprovision
 the application type, use the following command:
 
-```azurecli
+```shell
 sfctl application unprovision --application-type-name TestAppType --application-type-version 1.0
 ```
 
@@ -146,15 +146,15 @@ of the application. For more information, see the documentation on
 
 To perform an upgrade, first provision the next version of the application using the same commands as before:
 
-```azurecli
+```shell
 sfctl application upload --path ~/app_package_dir_2
 sfctl application provision --application-type-build-path app_package_dir_2
 sfctl store delete --content-path app_package_dir_2
 ```
 
 It is recommended then to perform a monitored automatic upgrade, launch the upgrade by running the following command:
 
-```azurecli
+```shell
 sfctl application upgrade --app-id TestApp --app-version 2.0.0 --parameters "{\"test\":\"value\"}" --mode Monitored
 ```
 

articles/service-fabric/service-fabric-cli.md

@@ -36,7 +36,7 @@ The Service Fabric CLI is meant to support the latest runtime version of the Ser
 
 You can optionally specify a target version of the CLI to install by suffixing the `pip install` command with `==<version>`. For example, for version 1.1.0 the syntax would be:
 
-```
+```shell
 pip install -I sfctl==1.1.0
 ```
 
@@ -62,14 +62,14 @@ For Windows 10, Windows Server 2016, and Windows Server 2012 R2, use the standar
 
 Now you can open a new command window and get the version of both Python and pip.
 
-```bat
+```shell
 python --version
 pip --version
 ```
 
 Then run the following command to install the Azure Service Fabric CLI (sfctl) and view the CLI help page:
 
-```bat
+```shell
 pip install sfctl
 sfctl -h
 ```
@@ -98,7 +98,7 @@ Be sure that `~/.local/bin` is accessible from the `$PATH`:
 
 ```bash
 export PATH=$PATH:~/.local/bin
-echo "export PATH=$PATH:~/.local/bin" >> .bashrc
+echo "export PATH=$PATH:~/.local/bin" >> .shellrc
 ```
 
 If the installation on Windows subsystem for Linux fails with incorrect folder permissions, it may be necessary to try again with elevated permissions:
@@ -143,7 +143,7 @@ Commands are always prefixed with `sfctl`. For general information about all the
 
 Commands follow a repeatable structure, with the target of the command preceding the verb or the action.
 
-```azurecli
+```shell
 sfctl <object> <action>
 ```
 
@@ -156,15 +156,15 @@ Before you perform any operations, you must select a cluster to connect to. For
 > [!WARNING]
 > Do not use unsecured Service Fabric clusters in a production environment.
 
-```azurecli
+```shell
 sfctl cluster select --endpoint http://testcluster.com:19080
 ```
 
 The cluster endpoint must be prefixed by `http` or `https`. It must include the port for the HTTP gateway. The port and address are the same as the Service Fabric Explorer URL.
 
 For clusters that are secured with a certificate, you can specify a PEM-encoded certificate. The certificate can be specified as a single file or as a cert and a key pair. If it is a self-signed certificate that is not CA signed, you can pass the `--no-verify` option to bypass CA verification.
 
-```azurecli
+```shell
 sfctl cluster select --endpoint https://testsecurecluster.com:19080 --pem ./client.pem --no-verify
 ```
 
@@ -177,7 +177,7 @@ Cluster connection information persists across multiple Service Fabric CLI sessi
 
 For example, to get the Service Fabric cluster health state, use the following command:
 
-```azurecli
+```shell
 sfctl cluster health
 ```
 
@@ -214,13 +214,13 @@ Here are some suggestions and tips for solving common problems.
 
 The Service Fabric CLI supports client-side certificates as PEM (.pem extension) files. If you use PFX files from Windows, you must convert those certificates to PEM format. To convert a PFX file to a PEM file, use the following command:
 
-```bash
+```shell
 openssl pkcs12 -in certificate.pfx -out mycert.pem -nodes
 ```
 
 Similarly, to convert from a PEM file to a PFX file, you can use the following command (no password is being provided here):
 
-```bash
+```shell
 openssl  pkcs12 -export -out Certificates.pfx -inkey Certificates.pem -in Certificates.pem -passout pass:'' 
 ```
 
@@ -242,21 +242,21 @@ Detailed logs often are helpful when you debug or report a problem. The `--debug
 
 For help with a specific command or a group of commands, use the `-h` flag.
 
-```azurecli
+```shell
 sfctl application -h
 ```
 
 Here is another example:
 
-```azurecli
+```shell
 sfctl application create -h
 ```
 
 ## Updating the Service Fabric CLI 
 
 To update the Service Fabric CLI, run the following commands (replace `pip` with `pip3` depending on what you chose during your original install):
 
-```bash
+```shell
 pip uninstall sfctl
 pip install sfctl
 ```

articles/service-fabric/service-fabric-cluster-scale-up-down.md

@@ -99,7 +99,7 @@ To keep the nodes of the cluster evenly distributed across upgrade and fault dom
 Get-ServiceFabricNode | Sort-Object NodeInstanceId -Descending | Select-Object -First 1
 ```
 
-```azurecli
+```shell
 sfctl node list --query "sort_by(items[*], &name)[-1]"
 ```
 
@@ -181,7 +181,7 @@ else
 
 In the **sfctl** code below, the following command is used to get the **node-name** value of the last-created node: `sfctl node list --query "sort_by(items[*], &name)[-1].name"`
 
-```azurecli
+```shell
 # Inform the node that it is going to be removed
 sfctl node disable --node-name _nt1vm_5 --deactivation-intent 4 -t 300
 

articles/service-fabric/service-fabric-connect-to-secure-cluster.md

@@ -22,15 +22,15 @@ You can connect to a cluster using the `sfctl cluster select` command.
 Client certificates can be specified in two different fashions, either as a cert and key pair, or as a single PFX
 file. For password protected PEM files, you will be prompted automatically to enter the password. If you obtained the client certificate as a PFX file, first convert the PFX file to a PEM file using the following command. 
 
-```bash
+```shell
 openssl pkcs12 -in your-cert-file.pfx -out your-cert-file.pem -nodes -passin pass:your-pfx-password
 ```
 
 If your .pfx file is not password protected, use -passin pass: for the last parameter.
 
 To specify the client certificate as a pem file, specify the file path in the `--pem` argument. For example:
 
-```azurecli
+```shell
 sfctl cluster select --endpoint https://testsecurecluster.com:19080 --pem ./client.pem
 ```
 
@@ -39,7 +39,7 @@ Password protected pem files will prompt for password prior to running any comma
 To specify a cert, key pair use the `--cert` and `--key` arguments to specify the file paths to each respective
 file.
 
-```azurecli
+```shell
 sfctl cluster select --endpoint https://testsecurecluster.com:19080 --cert ./client.crt --key ./keyfile.key
 ```
 
@@ -49,14 +49,14 @@ verification, specify the `--no-verify` option. For example:
 > [!WARNING]
 > Do not use the `no-verify` option when connecting to production Service Fabric clusters.
 
-```azurecli
+```shell
 sfctl cluster select --endpoint https://testsecurecluster.com:19080 --pem ./client.pem --no-verify
 ```
 
 In addition, you can specify paths to directories of trusted CA certs, or individual certs. To specify these
 paths, use the `--ca` argument. For example:
 
-```azurecli
+```shell
 sfctl cluster select --endpoint https://testsecurecluster.com:19080 --pem ./client.pem --ca ./trusted_ca
 ```
 

articles/service-fabric/service-fabric-docker-compose.md

@@ -64,37 +64,37 @@ Get-ServiceFabricComposeDeploymentUpgrade -DeploymentName TestContainerApp
 
 Alternatively, you can use the following Service Fabric CLI command:
 
-```azurecli
+```shell
 sfctl compose create --deployment-name TestContainerApp --file-path docker-compose.yml [ [ --user --encrypted-pass ] | [ --user --has-pass ] ] [ --timeout ]
 ```
 
 After you've created the deployment, you can check its status by using the following command:
 
-```azurecli
+```shell
 sfctl compose status --deployment-name TestContainerApp [ --timeout ]
 ```
 
 To delete the Compose deployment, use the following command:
 
-```azurecli
+```shell
 sfctl compose remove  --deployment-name TestContainerApp [ --timeout ]
 ```
 
 To start a Compose deployment upgrade, use the following command:
 
-```azurecli
+```shell
 sfctl compose upgrade --deployment-name TestContainerApp --file-path docker-compose-v2.yml [ [ --user --encrypted-pass ] | [ --user --has-pass ] ] [--upgrade-mode Monitored] [--failure-action Rollback] [ --timeout ]
 ```
 
 To rollback the Compose deployment upgrade, use the following command:
 
-```azurecli
+```shell
 sfctl compose upgrade-rollback --deployment-name TestContainerApp [ --timeout ]
 ```
 
 After upgrade is accepted, the upgrade progress could be tracked using the following command:
 
-```azurecli
+```shell
 sfctl compose upgrade-status --deployment-name TestContainerApp
 ```