Skip to content

Commit 44b74ed

Browse files
committed
Update: Add documentation on converting number-encoded tokens to strings
1 parent 006c940 commit 44b74ed

File tree

5 files changed

+1598
-75
lines changed

5 files changed

+1598
-75
lines changed

v2/cli.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -337,7 +337,7 @@ The CDK CLI actually runs your app and synthesizes fresh templates before most o
337337

338338
See `cdk synth --help` for all available options\. A few of the most frequently used options are covered in the following section\.
339339

340-
### Specify context values<a name="w92aac69c33c11"></a>
340+
### Specify context values<a name="w94aac69c33c11"></a>
341341

342342
Use the `--context` or `-c` option to pass [runtime context](context.md) values to your CDK app\.
343343

@@ -356,15 +356,15 @@ When deploying multiple stacks, the specified context values are normally passed
356356
cdk synth --context Stack1:key=value Stack2:key=value Stack1 Stack2
357357
```
358358

359-
### Specify display format<a name="w92aac69c33c13"></a>
359+
### Specify display format<a name="w94aac69c33c13"></a>
360360

361361
By default, the synthesized template is displayed in YAML format\. Add the `--json` flag to display it in JSON format instead\.
362362

363363
```
364364
cdk synth --json MyStack
365365
```
366366

367-
### Specify the output directory<a name="w92aac69c33c15"></a>
367+
### Specify the output directory<a name="w94aac69c33c15"></a>
368368

369369
Add the `--output` \(`-o`\) option to write the synthesized templates to a directory other than `cdk.out`\.
370370

@@ -440,7 +440,7 @@ Git\-style wildcards, both `*` and `**`, can be used in the `"watch"` and `"buil
440440
**Important**
441441
Watch mode is not recommended for production deployments\.
442442

443-
### Specify AWS CloudFormation parameters<a name="w92aac69c35c19"></a>
443+
### Specify AWS CloudFormation parameters<a name="w94aac69c35c19"></a>
444444

445445
The CDK CLI supports specifying AWS CloudFormation [parameters](parameters.md) at deployment\. You may provide these on the command line following the `--parameters` flag\.
446446

@@ -462,7 +462,7 @@ cdk deploy MyStack YourStack --parameters MyStack:uploadBucketName=UploadBucket
462462

463463
By default, the AWS CDK retains values of parameters from previous deployments and uses them in later deployments if they are not specified explicitly\. Use the `--no-previous-parameters` flag to require all parameters to be specified\.
464464

465-
### Specify outputs file<a name="w92aac69c35c21"></a>
465+
### Specify outputs file<a name="w94aac69c35c21"></a>
466466

467467
If your stack declares AWS CloudFormation outputs, these are normally displayed on the screen at the conclusion of deployment\. To write them to a file in JSON format, use the `--outputs-file` flag\.
468468

v2/serverless_example.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1494,7 +1494,7 @@ CdkHelloWorldStack: destroying... [1/1]
14941494

14951495
## Troubleshooting<a name="serverless-example-troubleshooting"></a>
14961496

1497-
### Error: \{“message”: “Internal server error”\}%<a name="w92aac81c11c55b5"></a>
1497+
### Error: \{“message”: “Internal server error”\}%<a name="w94aac81c11c55b5"></a>
14981498

14991499
When invoking the deployed Lambda function, you receive this error\. This error could occur for multiple reasons\.
15001500

v2/tagging.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ awscdk.Tags_Of(myConstruct).Remove(jsii.String("key"), &awscdk.TagProps{})
112112

113113
If you are using `Stage` constructs, apply the tag at the `Stage` level or below\. Tags are not applied across `Stage` boundaries\.
114114

115-
## Tag priorities<a name="w92aac13c73c17"></a>
115+
## Tag priorities<a name="w94aac13c73c17"></a>
116116

117117
The AWS CDK applies and removes tags recursively\. If there are conflicts, the tagging operation with the highest priority wins\. \(Priorities are set using the optional `priority` property\.\) If the priorities of two operations are the same, the tagging operation closest to the bottom of the construct tree wins\. By default, applying a tag has a priority of 100 \(except for tags added directly to an AWS CloudFormation resource, which has a priority of 50\)\. The default priority for removing a tag is 200\.
118118

0 commit comments

Comments
 (0)