From 860434141e348c14f73d89ce41ca602be76226bd Mon Sep 17 00:00:00 2001 From: Jeff Escalante Date: Thu, 2 Apr 2020 12:38:39 -0400 Subject: [PATCH] patch dollar sign escaping issue --- website/pages/docs/builders/amazon/index.mdx | 4 ++-- website/pages/docs/builders/azure/arm.mdx | 2 +- website/pages/docs/provisioners/chef-client.mdx | 4 ++-- website/pages/docs/provisioners/chef-solo.mdx | 4 ++-- .../pages/guides/packer-on-cicd/build-virtualbox-image.mdx | 2 +- website/pages/intro/getting-started/build-image.mdx | 2 +- website/pages/intro/getting-started/parallel-builds.mdx | 4 ++-- 7 files changed, 11 insertions(+), 11 deletions(-) diff --git a/website/pages/docs/builders/amazon/index.mdx b/website/pages/docs/builders/amazon/index.mdx index 4e1221b0e..027e0a2f2 100644 --- a/website/pages/docs/builders/amazon/index.mdx +++ b/website/pages/docs/builders/amazon/index.mdx @@ -96,8 +96,8 @@ Usage: ### Shared Credentials file You can use an AWS credentials file to specify your credentials. The default -location is \$HOME/.aws/credentials on Linux and OS X, or -"%USERPROFILE%.aws\\credentials" for Windows users. If we fail to detect +location is `$HOME/.aws/credentials` on Linux and OS X, or +`%USERPROFILE%.aws\credentials` for Windows users. If we fail to detect credentials inline, or in the environment, Packer will check this location. You can optionally specify a different location in the configuration by setting the environment with the `AWS_SHARED_CREDENTIALS_FILE` variable. diff --git a/website/pages/docs/builders/azure/arm.mdx b/website/pages/docs/builders/azure/arm.mdx index b96529b2f..9c6a9e8d2 100644 --- a/website/pages/docs/builders/azure/arm.mdx +++ b/website/pages/docs/builders/azure/arm.mdx @@ -12,7 +12,7 @@ Type: `azure-arm` Packer supports building VHDs and Managed Images in [Azure Resource Manager](https://azure.microsoft.com/en-us/documentation/articles/resource-group-overview/). -Azure provides new users a [\$200 credit for the first 30 +Azure provides new users a [`$200` credit for the first 30 days](https://azure.microsoft.com/en-us/free/); after which you will incur costs for VMs built and stored using Packer. diff --git a/website/pages/docs/provisioners/chef-client.mdx b/website/pages/docs/provisioners/chef-client.mdx index 800b90457..fb4822c73 100644 --- a/website/pages/docs/provisioners/chef-client.mdx +++ b/website/pages/docs/provisioners/chef-client.mdx @@ -139,8 +139,8 @@ configuration is actually required. - `staging_directory` (string) - This is the directory where all the configuration of Chef by Packer will be placed. By default this is - "/tmp/packer-chef-client" when guest_os_type unix and - "\$env:TEMP/packer-chef-client" when windows. This directory doesn't need to + `/tmp/packer-chef-client` when guest_os_type unix and + `$env:TEMP/packer-chef-client` when windows. This directory doesn't need to exist but must have proper permissions so that the user that Packer uses is able to create directories and write into this folder. By default the provisioner will create and chmod 0777 this directory. diff --git a/website/pages/docs/provisioners/chef-solo.mdx b/website/pages/docs/provisioners/chef-solo.mdx index a6fc93183..28039b6ee 100644 --- a/website/pages/docs/provisioners/chef-solo.mdx +++ b/website/pages/docs/provisioners/chef-solo.mdx @@ -109,8 +109,8 @@ configuration is actually required, but at least `run_list` is recommended. - `staging_directory` (string) - This is the directory where all the configuration of Chef by Packer will be placed. By default this is - "/tmp/packer-chef-solo" when guest_os_type unix and - "\$env:TEMP/packer-chef-solo" when windows. This directory doesn't need to + `/tmp/packer-chef-solo` when guest_os_type unix and + `$env:TEMP/packer-chef-solo` when windows. This directory doesn't need to exist but must have proper permissions so that the user that Packer uses is able to create directories and write into this folder. If the permissions are not correct, use a shell provisioner prior to this to configure it diff --git a/website/pages/guides/packer-on-cicd/build-virtualbox-image.mdx b/website/pages/guides/packer-on-cicd/build-virtualbox-image.mdx index 644e8b858..e8a7bb4d8 100644 --- a/website/pages/guides/packer-on-cicd/build-virtualbox-image.mdx +++ b/website/pages/guides/packer-on-cicd/build-virtualbox-image.mdx @@ -26,7 +26,7 @@ directly, but you may also fork it for the same results. For the purposes of this example, we will run on a bare-metal instance from [Packet](https://www.packet.net/). If you are a first time user of Packet, the Packet team has provided HashiCorp the coupon code `hashi25` which you can use -for \$25 off to test out this guide and up to 30% if you decide to +for `$25` off to test out this guide and up to 30% if you decide to reserve ongoing servers (email help@packet.net for details). You can use a `baremetal_0` server type for testing, but for regular use, the `baremetal_1` instance may be a better option. diff --git a/website/pages/intro/getting-started/build-image.mdx b/website/pages/intro/getting-started/build-image.mdx index 7f3fd3951..cc70a3704 100644 --- a/website/pages/intro/getting-started/build-image.mdx +++ b/website/pages/intro/getting-started/build-image.mdx @@ -180,7 +180,7 @@ they're built, it is up to you to launch or destroy them as you see fit. After running the above example, your AWS account now has an AMI associated with it. AMIs are stored in S3 by Amazon, so unless you want to be charged -about \$0.01 per month, you'll probably want to remove it. Remove the AMI by +about `$0.01` per month, you'll probably want to remove it. Remove the AMI by first deregistering it on the [AWS AMI management page](https://console.aws.amazon.com/ec2/home?region=us-east-1#s=Images). Next, delete the associated snapshot on the [AWS snapshot management diff --git a/website/pages/intro/getting-started/parallel-builds.mdx b/website/pages/intro/getting-started/parallel-builds.mdx index dbf699dc4..41fca4d31 100644 --- a/website/pages/intro/getting-started/parallel-builds.mdx +++ b/website/pages/intro/getting-started/parallel-builds.mdx @@ -43,10 +43,10 @@ this example. In order to do this, you'll need an account with DigitalOcean. [Sign up for an account now](https://www.digitalocean.com/). It is free to sign up. Because the -"droplets" (servers) are charged hourly, you _will_ be charged \$0.01 for every +"droplets" (servers) are charged hourly, you _will_ be charged `$0.01` for every image you create with Packer. If you're not okay with this, just follow along. -!> **Warning!** You _will_ be charged \$0.01 by DigitalOcean per image +!> **Warning!** You _will_ be charged `$0.01` by DigitalOcean per image created with Packer because of the time the "droplet" is running. Once you sign up for an account, grab your API token from the [DigitalOcean API