Skip to content

Commit 6517fd9

Browse files
committed
Updated README
1 parent 4d2d5f6 commit 6517fd9

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -55,6 +55,7 @@ Start with this configuration file template and modify to fit your needs (trigge
5555
"awsRegion": "us-east-1",
5656
"autoIncrementVersion": true,
5757
"cfDistributionID": "1XY234ABC",
58+
"cacheBehaviorPath": "default",
5859
"lambdaCodeS3Bucket": "my-s3-bucket",
5960
"cfTriggers": [
6061
{
@@ -208,6 +209,10 @@ Updates the CloudFront configuration to point to the newly published (or previou
208209

209210
#### Optional options
210211

212+
- CacheBehavior PathPattern
213+
- CLI: `--cache-behavior-path`
214+
- Config: `cacheBehaviorPath`
215+
- Note: used to identify the cache behavior to attach the Lambdas to. If left blank, will default to the DefaultCacheBehavior
211216
- Lambda code version (overrides auto-increment)
212217
- CLI: `--lambda-version`
213218
- Config: none
@@ -288,11 +293,6 @@ stage('Deploy - QA') {
288293

289294
Then I have a downstream job to run the rest of the Prod commands to activate them.
290295

291-
## Known Limitations
292-
293-
- Currently, this will only modify triggers on the default cache behavior of a CloudFront distribution.
294-
If requested, support for additional behaviors can be added.
295-
296296
## Contributing
297297

298298
Feel free to open a pull request.

0 commit comments

Comments
 (0)