Revert to single quotes around JSON blocks

Author: jhlodin

src/current/_includes/cockroachcloud/backups/cloud-api-backup-settings.md

@@ -43,7 +43,7 @@ To configure the frequency and retention of managed backups, send a `PUT` reques
 curl --request PUT \
 --url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/backups-config \
 --header "Authorization: Bearer {secret_key}" \
---data "{"enabled": true, "frequency_minutes": 30, "retention_days": 2}"
+--data '{"enabled": true, "frequency_minutes": 30, "retention_days": 2}'
 ~~~
 
 Set the following:

src/current/_includes/cockroachcloud/backups/cloud-api-restore-endpoint.md

@@ -25,10 +25,10 @@ To restore a cluster to a recent managed backup, send a `POST` request to the `/
 curl --request POST \
 --url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/restores \
 --header "Authorization: Bearer {secret_key}" \
---json "{
+--json '{
     "source_cluster_id": "{cluster_id}",
     "type": "CLUSTER"
-}"
+}'
 ~~~
 
 By default, the restore job uses the most recent backup stored within the last 7 days on the cluster specified in `source_cluster_id`. To restore a specific backup, include the `backup_id` field and specify a backup ID from the [managed backups list](#view-managed-backups):
@@ -38,10 +38,10 @@ By default, the restore job uses the most recent backup stored within the last 7
 curl --request POST \
 --url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/restores \
 --header "Authorization: Bearer {secret_key}" \
---json "{
+--json '{
     "backup_id": "example-2d25-4a64-8172-28af7a0d41cc",
     "type": "CLUSTER"
-}"
+}'
 ~~~
 
 {% if page.name == "managed-backups-advanced.md" %}
@@ -52,10 +52,10 @@ To restore a cluster backup into a different cluster, ensure that the destinatio
 curl --request POST \
 --url https://cockroachlabs.cloud/api/v1/clusters/{destination_cluster_id}/restores \
 --header "Authorization: Bearer {secret_key}" \
---json "{
+--json '{
     "source_cluster_id": "{source_cluster_id}",
     "type": "CLUSTER"
-}"
+}'
 ~~~
 
 You can specify additional options for the restore job in the `restore_opts` object. For more information, see the [API endpoint documentation](https://www.cockroachlabs.com/docs/api/cloud/v1#get-/api/v1/clusters/-cluster_id-/restores-config).
@@ -85,7 +85,7 @@ To restore one or more databases from a cluster's managed backup, send a `POST`
 curl --request POST \
 --url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/restores \
 --header "Authorization: Bearer {secret_key}" \
---json "{
+--json '{
     "source_cluster_id": "{cluster_id}",
     "type": "DATABASE",
     "objects": [
@@ -96,7 +96,7 @@ curl --request POST \
             "database": "movr"
         }
     ]
-}"
+}'
 ~~~
 
 By default, the database is restored into the original database name from the managed backup. To restore the database contents into a new database, include the field `restore_opts.new_db_name` with the new database name. You can only restore one database at a time when using this option.
@@ -106,7 +106,7 @@ By default, the database is restored into the original database name from the ma
 curl --request POST \
 --url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/restores \
 --header "Authorization: Bearer {secret_key}" \
---json "{
+--json '{
     "source_cluster_id": "{cluster_id}",
     "type": "DATABASE",
     "objects": [
@@ -117,7 +117,7 @@ curl --request POST \
     "restore_opts": {
         "new_db_name": "tpcc2"
     }
-}"
+}'
 ~~~
 
 To restore from a specific backup rather than the most recently created managed backup, include the `backup_id` field specifying a backup ID:
@@ -127,15 +127,15 @@ To restore from a specific backup rather than the most recently created managed
 curl --request POST \
 --url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/restores \
 --header "Authorization: Bearer {secret_key}" \
---json "{
+--json '{
     "backup_id": "example-2d25-4a64-8172-28af7a0d41cc",
     "type": "DATABASE",
     "objects": [
         {
             "database": "tpcc"
         }
     ]
-}"
+}'
 ~~~
 
 To restore a database from a source cluster's managed backup into a different cluster, send the restore request to the destination cluster ID. Specify the ID of the backup's cluster as `source_cluster_id`. Both the source cluster and the destination cluster must use the Advanced plan.
@@ -145,15 +145,15 @@ To restore a database from a source cluster's managed backup into a different cl
 curl --request POST \
 --url https://cockroachlabs.cloud/api/v1/clusters/{destination_cluster_id}/restores \
 --header "Authorization: Bearer {secret_key}" \
---json "{
+--json '{
     "source_cluster_id": "{source_cluster_id}",
     "type": "DATABASE",
     "objects": [
         {
             "database": "tpcc"
         }
     ]
-}"
+}'
 ~~~
 
 You can specify additional options for the restore jobs in the `restore_opts` object. For more information, see the [API endpoint documentation](https://www.cockroachlabs.com/docs/api/cloud/v1#get-/api/v1/clusters/-cluster_id-/restores-config).
@@ -180,7 +180,7 @@ To restore a one or more tables from a cluster's managed backup, send a `POST` r
 curl --request POST \
 --url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/restores \
 --header "Authorization: Bearer {secret_key}" \
---json "{
+--json '{
     "source_cluster_id": "{cluster_id}",
     "type": "TABLE",
     "objects": [
@@ -195,7 +195,7 @@ curl --request POST \
             "table": "customer"
         }
     ]
-}"
+}'
 ~~~
 
 By default, the table is restored into the original database name from the managed backup. To restore the table into a different database, include the field `restore_opts.into_db` with the desired database name. The following example restores the `tpcc.public.warehouse` table from the most recent managed backup into `tpcc2.public.warehouse` on the cluster:
@@ -205,7 +205,7 @@ By default, the table is restored into the original database name from the manag
 curl --request POST \
 --url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/restores \
 --header "Authorization: Bearer {secret_key}" \
---json "{
+--json '{
     "source_cluster_id": "{cluster_id}",
     "type": "TABLE",
     "objects": [
@@ -223,7 +223,7 @@ curl --request POST \
     "restore_opts": {
         "into_db": "tpcc2"
     }
-}"
+}'
 ~~~
 
 To restore from a specific backup rather than the most recently created managed backup, include the `backup_id` field specifying a backup ID:
@@ -233,7 +233,7 @@ To restore from a specific backup rather than the most recently created managed
 curl --request POST \
 --url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/restores \
 --header "Authorization: Bearer {secret_key}" \
---json "{
+--json '{
     "backup_id": "example-2d25-4a64-8172-28af7a0d41cc",
     "type": "TABLE",
     "objects": [
@@ -243,7 +243,7 @@ curl --request POST \
             "table": "warehouse"
         }
     ]
-}"
+}'
 ~~~
 
 To restore a table from a source cluster's managed backup into a different cluster, send the restore request to the destination cluster ID. Specify the ID of the backup's cluster as `source_cluster_id`. Both the source cluster and the destination cluster must use the Advanced plan.
@@ -253,7 +253,7 @@ To restore a table from a source cluster's managed backup into a different clust
 curl --request POST \
 --url https://cockroachlabs.cloud/api/v1/clusters/{destination_cluster_id}/restores \
 --header "Authorization: Bearer {secret_key}" \
---json "{
+--json '{
     "source_cluster_id": "{source_cluster_id}",
     "type": "TABLE",
     "objects": [
@@ -263,7 +263,7 @@ curl --request POST \
             "table": "warehouse"
         }
     ]
-}"
+}'
 ~~~
 
 You can specify additional options for the restore jobs in the `restore_opts` object. For more information, see the [API endpoint documentation](https://www.cockroachlabs.com/docs/api/cloud/v1#get-/api/v1/clusters/-cluster_id-/restores-config).

src/current/cockroachcloud/aws-privatelink.md

@@ -80,7 +80,7 @@ curl --request POST \
   --url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/networking/private-endpoint-trusted-owners \
   --header "Authorization: Bearer {bearer_token}" \
   --header "content-type: application/json" \
-  --data "{"external_owner_id":"{aws_account_id}","type":"AWS_ACCOUNT_ID"}"
+  --data '{"external_owner_id":"{aws_account_id}","type":"AWS_ACCOUNT_ID"}'
 ~~~
 
 Replace:

src/current/cockroachcloud/cloud-api.md

@@ -108,7 +108,7 @@ The service account associated with the secret key must have the Cluster Admin o
 curl --request POST \
   --url https://cockroachlabs.cloud/api/v1/clusters \
   --header "Authorization: Bearer {secret_key}" \
-  --json "{"name":"{cluster_name}","provider":"{cloud_provider}","plan":"BASIC","spec":{"serverless":{"regions":["{region_name}"]}}}"
+  --json '{"name":"{cluster_name}","provider":"{cloud_provider}","plan":"BASIC","spec":{"serverless":{"regions":["{region_name}"]}}}'
 ~~~
 
 </section>
@@ -154,7 +154,7 @@ For example, to create a new Basic cluster named `basic-test` using GCP as the c
 curl --request POST \
   --url https://cockroachlabs.cloud/api/v1/clusters \
   --header "Authorization: Bearer {secret_key}" \
-  --json "{"name":"basic-test","provider":"GCP","plan":"BASIC","spec":{"serverless":{"regions":["us-central1"]}}}"
+  --json '{"name":"basic-test","provider":"GCP","plan":"BASIC","spec":{"serverless":{"regions":["us-central1"]}}}'
 ~~~
 
 </section>
@@ -203,7 +203,7 @@ The service account associated with the secret key must have the Cluster Admin o
 curl --request POST \
   --url https://cockroachlabs.cloud/api/v1/clusters \
   --header "Authorization: Bearer {secret_key}" \
-  --json "{"name":"{cluster_name}","provider":"{cloud_provider}","plan":"STANDARD","spec":{"serverless":{"regions":["{region_name}"],"usage_limits":{"provisioned_virtual_cpus":"2"}}}}"
+  --json '{"name":"{cluster_name}","provider":"{cloud_provider}","plan":"STANDARD","spec":{"serverless":{"regions":["{region_name}"],"usage_limits":{"provisioned_virtual_cpus":"2"}}}}'
 ~~~
 
 </section>
@@ -253,7 +253,7 @@ For example, to create a new Standard cluster named `notorious-moose` using the
 curl --request POST \
   --url https://cockroachlabs.cloud/api/v1/clusters \
   --header "Authorization: Bearer {secret_key}" \
-  --json "{"name":"notorious-moose","provider":"GCP","plan":"STANDARD","spec":{"serverless":{"regions":["us-central1"],"usage_limits":{"provisioned_virtual_cpus":"2"}}}}"
+  --json '{"name":"notorious-moose","provider":"GCP","plan":"STANDARD","spec":{"serverless":{"regions":["us-central1"],"usage_limits":{"provisioned_virtual_cpus":"2"}}}}'
 ~~~
 
 </section>
@@ -305,7 +305,7 @@ The service account associated with the secret key must have the Cluster Admin o
 curl --request POST \
   --url https://cockroachlabs.cloud/api/v1/clusters \
   --header "Authorization: Bearer {secret_key}" \
-  --json "{"name":"{cluster_name}","provider":"{cloud_provider}","plan":"ADVANCED","spec":{"dedicated":{"region_nodes":{"{region_name}":3},"hardware":{"machine_spec":{"num_virtual_cpus":{num_vcpus}}},"cockroach_version":"{version}"}}}"
+  --json '{"name":"{cluster_name}","provider":"{cloud_provider}","plan":"ADVANCED","spec":{"dedicated":{"region_nodes":{"{region_name}":3},"hardware":{"machine_spec":{"num_virtual_cpus":{num_vcpus}}},"cockroach_version":"{version}"}}}'
 ~~~
 
 </section>
@@ -360,7 +360,7 @@ For example, to create a new Advanced cluster named `advanced-test` using AWS as
 curl --request POST \
   --url https://cockroachlabs.cloud/api/v1/clusters \
   --header "Authorization: Bearer {secret_key}" \
-  --json "{"name":"advanced-test","provider":"AWS","plan":"ADVANCED","spec":{"dedicated":{"region_nodes":{"us-east-1":3},"hardware":{"machine_spec":{"num_virtual_cpus":4}},"cockroach_version":"v23.1.2"}}}"
+  --json '{"name":"advanced-test","provider":"AWS","plan":"ADVANCED","spec":{"dedicated":{"region_nodes":{"us-east-1":3},"hardware":{"machine_spec":{"num_virtual_cpus":4}},"cockroach_version":"v23.1.2"}}}'
 ~~~
 
 </section>
@@ -497,7 +497,7 @@ The service account associated with the secret key must have the Cluster Admin o
 curl --request PATCH \
   --url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id} \
   --header "Authorization: Bearer {secret_key}" \
-  --json "{"serverless":{"usage_limits":{"storage_mib_limit":"5242880","request_unit_limit":"50000000"}}}"
+  --json '{"serverless":{"usage_limits":{"storage_mib_limit":"5242880","request_unit_limit":"50000000"}}}'
 ~~~
 
 </section>
@@ -556,7 +556,7 @@ The service account associated with the secret key must have the Cluster Admin o
 curl --request PATCH \
   --url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id} \
   --header "Authorization: Bearer {secret_key}" \
-  --json "{"serverless":{"usage_limits":{"provisioned_virtual_cpus":"{provisioned_virtual_cpus}"}}}"
+  --json '{"serverless":{"usage_limits":{"provisioned_virtual_cpus":"{provisioned_virtual_cpus}"}}}'
 ~~~
 
 </section>
@@ -600,7 +600,7 @@ For example, to change the number of vCPUs per node to 8:
 curl --request PATCH \
   --url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id} \
   --header "Authorization: Bearer {secret_key}" \
-  --json "{
+  --json '{
     "spec": {
       "dedicated": {
         "hardware": {
@@ -610,7 +610,7 @@ curl --request PATCH \
         }
       }
     }
-  }"
+  }'
 ~~~
 
 To change the number of nodes in a region:
@@ -620,15 +620,15 @@ To change the number of nodes in a region:
 curl --request PATCH \
   --url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id} \
   --header "Authorization: Bearer {secret_key}" \
-  --json "{
+  --json '{
     "spec": {
       "dedicated": {
         "region_nodes": {
           "us-east-1": 5
         }
       }
     }
-  }"
+  }'
 ~~~
 
 Where `{cluster_id}` is the ID of your cluster and `{secret_key}` is your API key.
@@ -924,7 +924,7 @@ When possible, it is best practice to [limit each user's privileges]({% link coc
 curl --request POST \
   --url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/sql-users \
   --header "Authorization: Bearer {secret_key}" \
-  --json "{"name":"{sql_username}","password":"{password}"}"
+  --json '{"name":"{sql_username}","password":"{password}"}'
 ~~~
 
 Where:
@@ -1000,7 +1000,7 @@ The service account associated with the secret key must have the Cluster Admin o
 curl --request PUT \
   --url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/sql-users/{sql_username}/password \
   --header "Authorization: Bearer {secret_key}" \
-  --json "{"password":"{new_password}"}"
+  --json '{"password":"{new_password}"}'
 ~~~
 
 Where:
@@ -1035,7 +1035,7 @@ The service account associated with the secret key must have the Cluster Admin o
 curl --request PUT \
   --url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/maintenance-window \
   --header "Authorization: Bearer REPLACE_BEARER_TOKEN" \
-  --json "{"offset_duration":"{offset_duration}","window_duration":"{window_duration}"}"
+  --json '{"offset_duration":"{offset_duration}","window_duration":"{window_duration}"}'
 ~~~
 
 Where:
@@ -1094,7 +1094,7 @@ The service account associated with the secret key must have the Cluster Admin o
 curl --request PUT \
   --url https://cockroachlabs.cloud/api/v1/clusters/{cluster_id}/version-deferral \
   --header "Authorization: Bearer REPLACE_BEARER_TOKEN" \
-  --json "{"deferral_policy":"{deferral_policy}"}"
+  --json '{"deferral_policy":"{deferral_policy}"}'
 ~~~
 
 Where:

src/current/cockroachcloud/egress-perimeter-controls.md

@@ -115,7 +115,7 @@ Essential external traffic destined to resources managed by Cockroach Labs is al
     --header "Authorization: Bearer $CC_API_KEY" \
     --header "Cc-Version: latest" \
     --url https://cockroachlabs.cloud/api/v1/clusters/$CLUSTER_ID/networking/egress-rules/egress-traffic-policy \
-    --data "{"allow_all":false}"
+    --data '{"allow_all":false}'
     ~~~
 
     ~~~txt