File tree Expand file tree Collapse file tree 1 file changed +5
-5
lines changed Expand file tree Collapse file tree 1 file changed +5
-5
lines changed Original file line number Diff line number Diff line change @@ -55,6 +55,7 @@ Start with this configuration file template and modify to fit your needs (trigge
55
55
"awsRegion" : " us-east-1" ,
56
56
"autoIncrementVersion" : true ,
57
57
"cfDistributionID" : " 1XY234ABC" ,
58
+ "cacheBehaviorPath" : " default" ,
58
59
"lambdaCodeS3Bucket" : " my-s3-bucket" ,
59
60
"cfTriggers" : [
60
61
{
@@ -208,6 +209,10 @@ Updates the CloudFront configuration to point to the newly published (or previou
208
209
209
210
#### Optional options
210
211
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
211
216
- Lambda code version (overrides auto-increment)
212
217
- CLI: ` --lambda-version `
213
218
- Config: none
@@ -288,11 +293,6 @@ stage('Deploy - QA') {
288
293
289
294
Then I have a downstream job to run the rest of the Prod commands to activate them.
290
295
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
-
296
296
## Contributing
297
297
298
298
Feel free to open a pull request.
You can’t perform that action at this time.
0 commit comments