change more commands to new shortcode

Author: dfangl

Diff for: content/en/docs/Integrations/architect/index.md

@@ -25,15 +25,15 @@ The ``` arclocal``` command has the same usage as the ```arc``` command, so you
 
 Create a test directory
 
-```bash
-mkdir architect_quickstart && cd architect_quickstart
-```
+{{< command >}}
+$ mkdir architect_quickstart && cd architect_quickstart
+{{< / command >}}
 
 then create an architect project
 
-```
-arclocal init
-```
+{{< command >}}
+$ arclocal init
+{{< / command >}}
 
 ### Deployment
 
@@ -43,9 +43,9 @@ Now you need to start LocalStack. The services you need to start are
  - cloudformation
 
 After LocalStack has started you can deploy your Architect setup via
-```
-arclocal deploy
-```
+{{< command >}}
+$ arclocal deploy
+{{< / command >}}
 
 ## Further reading
 

Diff for: content/en/docs/Integrations/aws-cli/index.md

@@ -68,14 +68,14 @@ The source code can be found on GitHub: https://github.com/localstack/awscli-loc
 
 You can install the `awslocal` command via `pip`:
 
-```
-pip install awscli-local[ver1]
-```
+{{< command >}}
+$ pip install awscli-local[ver1]
+{{< / command >}}
 
 Note that the command above also installs the latest version of the underlying AWS CLI version 1 (`awscli`) package. Use this command if you prefer to manage your own version of `awscli` (e.g., `v1`/`v2`) and install the wrapper script only:
-```
-pip install awscli-local
-```
+{{< command >}}
+$ pip install awscli-local
+{{< / command >}}
 
 {{< alert >}}
 **Note:** Automatic installation of AWS CLI version 2 is currently not supported yet (at the time of writing there is no official pypi package for `v2` available), but the `awslocal` technically also works with AWS CLI v2 (see [this section]({{< ref "#limitations" >}}) for more details).
@@ -107,11 +107,11 @@ To work around this issue, you have 2 options:
   We do not recommend this, but it is technically possible.
   Also, you should install these libraries in a Python virtualenv, to avoid version clashes with other libraries on your system:
 
-```bash
-virtualenv .venv
-. .venv/bin/activate
-pip install https://github.com/boto/botocore/archive/v2.zip https://github.com/aws/aws-cli/archive/v2.zip
-```
+{{< command >}}
+$ virtualenv .venv
+$ . .venv/bin/activate
+$ pip install https://github.com/boto/botocore/archive/v2.zip https://github.com/aws/aws-cli/archive/v2.zip
+{{< / command >}}
 
 ## AWS CLI v2
 
@@ -123,10 +123,11 @@ By default, the container running [amazon/aws-cli](https://docs.aws.amazon.com/c
 
 To ensure that the two docker containers can communicate create a network on the docker engine:
 
-```bash
+{{< command >}}
 $ docker network create localstack
 0c9cb3d37b0ea1bfeb6b77ade0ce5525e33c7929d69f49c3e5ed0af457bdf123
-```
+{{< / command >}}
+
 Then modify the `docker-compose.yml` specifying the network to use:
 
 ```yaml
@@ -138,24 +139,24 @@ networks:
 
 Run AWS Cli v2 docker container using this network (example):
 
-```bash
+{{< command >}}
 $ docker run --network localstack --rm -it amazon/aws-cli --endpoint-url=http://localstack:4566 lambda list-functions
 {
     "Functions": []
 }
-```
+{{< / command >}}
 
 If you use AWS CLI v2 from a docker container often, create an alias:
 
-```bash
+{{< command >}}
 $ alias laws='docker run --network localstack --rm -it amazon/aws-cli --endpoint-url=http://localstack:4566'
-```
+{{< / command >}}
 
 So you can type:
 
-```bash
+{{< command >}}
 $ laws lambda list-functions
 {
     "Functions": []
 }
-```
+{{< / command >}}

Diff for: content/en/docs/Integrations/pulumi/index.md

@@ -143,15 +143,15 @@ Make sure your LocalStack is running.
 For the example stack, the only required service is S3.
 After updating the stack configuration, and starting localstack, you can run:
 
-```bash
-pulumi up
-```
+{{< command >}}
+$ pulumi up
+{{< / command >}}
 
 once the stack update was performed, you can run:
 
-```bash
-awslocal s3 ls
-```
+{{< command >}}
+$ awslocal s3 ls
+{{< / command >}}
 
 Where you should see something like
 
@@ -169,34 +169,34 @@ You can find the source code repository here: https://github.com/localstack/pulu
 `pulumilocal` requires that you already have the `pulumi` command in your path.
 Then, simply run
 
-```bash
-pip install pulumi-local
-```
+{{< command >}}
+$ pip install pulumi-local
+{{< / command >}}
 
 then,
 
-```
+{{< command >}}
 pulumi version
 pulumilocal version
-```
+{{< / command >}}
 
 should output the same value.
 
 ### Use
 
 Instead of manually editing a stack configuration as explained earlier, you can run
 
-```bash
-pulumilocal init
-```
+{{< command >}}
+$ pulumilocal init
+{{< / command >}}
 
 which will create a `Pulumi.localstack.yaml` stack configuration, and initialize an additional stack named `localstack`.
 
 You can now run
 
-```bash
-pulumilocal up
-```
+{{< command >}}
+$ pulumilocal up
+{{< / command >}}
 
 to start the localstack stack.
 

Diff for: content/en/docs/Integrations/serverless-framework/index.md

@@ -68,9 +68,9 @@ resources:
 
 ## Install and configure Serverless-LocalStack Plugin
 To install the plugin, execute the following command in the root of your project.
-```bash
-npm install -D serverless-localstack
-```
+{{< command >}}
+$ npm install -D serverless-localstack
+{{< / command >}}
 
 Next, set up the plugin by adding the following properties to `serverless.yml`.
 ```yaml
@@ -126,14 +126,14 @@ else:
 You can now deploy your Serverless service to LocalStack.
 
 First, start LocalStack by running
-```bash
-localstack start
-```
+{{< command >}}
+$ localstack start
+{{< / command >}}
 
 Then deploy the endpoint by running
-```bash
-serverless deploy --stage local
-```
+{{< command >}}
+$ serverless deploy --stage local
+{{< / command >}}
 
 The expected result should be similar to:
 

Diff for: content/en/docs/Integrations/terraform/index.md

@@ -23,9 +23,9 @@ Apart from some information Terraform expects there are basically only two thing
 
 Before we start changing the configuration, create and change into a new directory for this sample
 
-```bash
-mkdir terraform_quickstart && cd terraform_quickstart
-```
+{{< command >}}
+$ mkdir terraform_quickstart && cd terraform_quickstart
+{{< / command >}}
 
 Inside this directory, create a file called `main.tf`.
 The following changes go into this file.
@@ -115,14 +115,14 @@ After starting LocalStack you can now deploy the s3 bucket via `terraform` and i
 
 All you need to do is to initialize Terraform
 
-```bash
-terraform init
-```
+{{< command >}}
+$ terraform init
+{{< / command >}}
 
 and then deploy the configuration
-```bash
-terraform deploy
-```
+{{< command >}}
+$ terraform deploy
+{{< / command >}}
 
 ## Endpoint configuration
 

Diff for: content/en/docs/Local AWS Services/apigatewayv2/index.md

@@ -23,7 +23,7 @@ functions:
 
 Upon deployment of the Serverless project, a new API Gateway V2 endpoint will be created in LocalStack. The [`awslocal`](https://github.com/localstack/awscli-local) CLI can be used to get the list of APIs, which should contain the WebSocket endpoint, e.g., `ws://localhost:4510` in the example below:
 
-```bash
+{{< command >}}
 $ awslocal apigatewayv2 get-apis
 {
     "Items": [{
@@ -32,7 +32,7 @@ $ awslocal apigatewayv2 get-apis
         ...
     }]
 }
-```
+{{< / command >}}
 
 Assuming your project contains a simple Lambda `handler.js` like this:
 

Diff for: content/en/docs/Local AWS Services/appsync/index.md

@@ -40,8 +40,8 @@ $util.toJson($context.result["Items"])
 ```
 
 Once things have been wired up properly, and assuming the ID of your GraphQL API is `"api123"`, you should be able to run the following GraphQL query to retrieve all items from the `"posts"` DynamoDB table:
-```bash
-curl -d '{"query":"query {getPosts{id{S}}}"}' http://localhost:4605/graphql/api123
-```
+{{< command >}}
+$ curl -d '{"query":"query {getPosts{id{S}}}"}' http://localhost:4605/graphql/api123
+{{< / command >}}
 
 For more details, please refer to the self-contained sample published in [this Github repository](https://github.com/localstack/localstack-pro-samples/tree/master/appsync-graphql-api).

Diff for: content/en/docs/Local AWS Services/athena/index.md

@@ -8,7 +8,8 @@ description: >
 LocalStack Pro ships with built-in support for [Athena](https://aws.amazon.com/athena), Amazon's serverless data warehouse and analytics platform. Athena uses [Presto](https://prestodb.github.io/) under the covers, and your Athena instance will be automatically configured with a Hive metastore that connects seamlessly to the LocalStack S3 API. That is, you can easily connect your local S3 buckets and query data directly from S3 via the powerful Athena query API.
 
 The following commands illustrate how to use Athena from the command line (assuming you have [`awslocal`](https://github.com/localstack/awscli-local) installed):
-```bash
+
+{{< command >}}
 $ awslocal athena start-query-execution --query-string 'SELECT 1, 2, 3'
 {
     "QueryExecutionId": "c9f453ad"
@@ -33,7 +34,7 @@ $ awslocal athena get-query-results --query-execution-id c9f453ad
     },
     "UpdateCount": 0
 }
-```
+{{< / command >}}
 
 {{< alert >}}**Note**:
 In order to use the Athena API, some additional dependencies have to be fetched from the network, including a Docker image of apprx. 1.5GB which includes Presto, Hive and other tools. These dependencies are automatically fetched when you start up the service, so please make sure you're on a decent internet connection when pulling the dependencies for the first time.

Diff for: content/en/docs/Local AWS Services/cloudfront/index.md

@@ -9,14 +9,15 @@ description: >
 LocalStack Pro supports creation of local CloudFront distributions, which allows you to transparently access your applications and file artifacts via CloudFront URLs like `https://abc123.cloudfront.net`.
 
 For example, take the following simple example which creates an S3 bucket, puts a small text file `hello.txt` to the bucket, and then creates a CloudFront distribution which makes the file accessible via a `https://abc123.cloudfront.net/hello.txt` proxy URL (where `abc123` is a placeholder for the real distribution ID):
-```bash
-awslocal s3 mb s3://bucket1
-echo 'Hello World' > /tmp/hello.txt
-awslocal s3 cp /tmp/hello.txt s3://bucket1/hello.txt --acl public-read
-domain=$(awslocal cloudfront create-distribution \
-  --origin-domain-name bucket1.s3.amazonaws.com | jq -r '.Distribution.DomainName')
-curl -k https://$domain/hello.txt
-```
+
+{{< command >}}
+$ awslocal s3 mb s3://bucket1
+$ echo 'Hello World' > /tmp/hello.txt
+$ awslocal s3 cp /tmp/hello.txt s3://bucket1/hello.txt --acl public-read
+$ domain=$(awslocal cloudfront create-distribution \
+   --origin-domain-name bucket1.s3.amazonaws.com | jq -r '.Distribution.DomainName')
+$ curl -k https://$domain/hello.txt
+{{< / command >}}
 
 {{< alert >}}
 **Note:** In order for CloudFront to be fully functional, your local DNS setup needs to be properly configured. See the section on [configuring the local DNS server]({{< ref "#configuring-local-dns-server" >}}) for details.

Diff for: content/en/docs/Local AWS Services/elasticsearch/index.md

@@ -22,7 +22,7 @@ You can go ahead and use [awslocal]({{< ref "aws-cli.md#localstack-aws-cli-awslo
 **Note**: The default Elasticsearch version used is 7.7.
 {{< /alert >}}
 
-```bash
+{{< command >}}
 $ awslocal es create-elasticsearch-domain --domain-name foobar
 {
     "DomainStatus": {
@@ -53,7 +53,7 @@ $ awslocal es create-elasticsearch-domain --domain-name foobar
         }
     }
 }
-```
+{{< / command >}}
 
 In the LocalStack log you will see something like
 
@@ -77,10 +77,10 @@ In the LocalStack log you will see something like
 
 and after some time, you should see that the `Created` state of the domain is set to `true`:
 
-```bash
+{{< command >}}
 $ awslocal es describe-elasticsearch-domain --domain-name foobar | jq ".DomainStatus.Created"
 true
-```
+{{< / command >}}
 
 ## Interact with the cluster
 
@@ -93,7 +93,7 @@ Additional domains share the same Elasticsearch cluster.
 
 For example:
 
-```bash
+{{< command >}}
 $ curl http://localhost:4571
 {
   "name" : "om",
@@ -112,12 +112,12 @@ $ curl http://localhost:4571
   },
   "tagline" : "You Know, for Search"
 }
-```
+{{< / command >}}
 
 Or the health endpoint:
 
-```bash
-curl -s http://localhost:4571/_cluster/health | jq .
+{{< command >}}
+$ curl -s http://localhost:4571/_cluster/health | jq .
 {
   "cluster_name": "elasticsearch",
   "status": "green",
@@ -135,4 +135,4 @@ curl -s http://localhost:4571/_cluster/health | jq .
   "task_max_waiting_in_queue_millis": 0,
   "active_shards_percent_as_number": 100
 }
-```
+{{< / command >}}