feat: Add cloudfront response header policy support #174
+310
−8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
joshAtRula
changed the title
Contributor
Author
|
@antonbabenko just tagging you here in case you missed the PR opening request. Thanks so much for your time on these modules! |
3 tasks
|
This PR has been automatically marked as stale because it has been open 30 days |
bryantbiggs
approved these changes
Nov 27, 2025
antonbabenko
pushed a commit
that referenced
this pull request
Nov 27, 2025
## [5.1.0](v5.0.1...v5.1.0) (2025-11-27) ### Features * Add cloudfront response header policy support ([#174](#174)) ([8488553](8488553))
Member
|
This PR is included in version 5.1.0 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
This PR adds support to the module to create cloudfront response headers, and then optionally reference them within the Cloudfront distro being created, enhancing the capabilities of the module to support a greater portion of the cloudfront experience.
Motivation and Context
My organization has cloudfront distros we're importing/recreating with this module that require custom response policies. Rather than diverge from the module substantially by augmenting our own implementation while vendoring this module in, why not help out? :)
Breaking Changes
No, this does not break any functionality.
How Has This Been Tested?
examples/*to demonstrate and validate my change(s)examples/*projectspre-commit run -aon my pull request