feat(cloudfront): managed cache policies UseOriginCacheControlHeaders #30379
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reason for this change
Cloudfront provides two additional managed cache policies,
UseOriginCacheControlHeaders
andUseOriginCacheControlHeaders-QueryStrings
that are not currently present as constants in the CDK. Five of the managed policies are currently provided as constants in the CDK.Description of changes
This PR adds two new constants,
USE_ORIGIN_CACHE_CONTROL_HEADERS
andUSE_ORIGIN_CACHE_CONTROL_HEADERS_QUERY_STRINGS
, in the style of the other existing constants for managed cache policies.Each are mapped to the policy ID provided by AWS:
USE_ORIGIN_CACHE_CONTROL_HEADERS
:83da9c7e-98b4-4e11-a168-04f0df8e2c65
USE_ORIGIN_CACHE_CONTROL_HEADERS_QUERY_STRINGS
:4cc15a8a-d715-48a4-82b8-cc0b614638fe
Tests are included for the two new constants, as well as covering a missing test for the
AMPLIFY
policy.Description of how you validated changes
The existing unit test was expanded to included the two new, plus one previously missing, constants.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license