Properly Acceptance Test CloudFront Distribution cache_behavior field_level_encryption_id #4101
Labels
service/cloudfront
Issues and PRs that pertain to the cloudfront service.
stale
Old or inactive issues managed by automation, if no further action taken these will get closed.
technical-debt
Addresses areas of the codebase that need refactoring or redesign.
tests
PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure.
Comments
bflad
added
tests
This was referenced Apr 6, 2018
Merged
|
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you! |
github-actions
bot
added
the
stale
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
ghost
locked and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Due to the breaking behavior introduced by v1.13.26 of the AWS SDK (#4091), the
field_level_encryption_idattribute was fast tracked for implementation intoaws_cloudfront_distributionresource (#4102). This is a ticket to circle back and add proper acceptance testing with respect to this new attribute when theaws_cloudfront_field_level_encryption_configresource is created as part of #4097.The text was updated successfully, but these errors were encountered: