Open
Description
SUMMARY
cloudfront_distribution compares the current and desired Aliases/LambdaFunctionAssociations configuration directly, meaning changes in the ordering of items in the lists causes an unnecessary update.
ISSUE TYPE
- Bug Report
COMPONENT NAME
cloudfront_distribution
STEPS TO REPRODUCE
cloudfront_distribution:
state: present
...
aliases: ...
EXPECTED RESULTS
List ordering for Aliases/LambdaFunctionAssociations should be ignored for idempotency checks.
ACTUAL RESULTS
--- before
+++ after
@@ -1,32 +1,30 @@
{
"Aliases": {
"Items": [
+ "aa.redacted.com",
+ "as.redacted.com",
+ "bs.redacted.com",
+ "ca.redacted.com",
+ "cs.redacted.com",
+ "ha.redacted.com",
+ "is.redacted.com",
+ "la.redacted.com",
+ "ls.redacted.com",
+ "redacted.com",
"rs.redacted.com",
"sa.redacted.com",
- "is.redacted.com",
- "la.redacted.com",
- "ca.redacted.com",
- "as.redacted.com",
- "ls.redacted.com",
- "redacted.com",
- "ss.redacted.com",
- "bs.redacted.com",
- "cs.redacted.com",
- "ha.redacted.com",
- "aa.redacted.com"
+ "ss.redacted.com"
]
},
"DefaultCacheBehavior": {
"LambdaFunctionAssociations": {
"Items": [
{
- "EventType": "origin-response",
- "IncludeBody": false,
+ "EventType": "origin-request",
"LambdaFunctionARN": "arn:aws:lambda:us-east-1:redacted"
},
{
- "EventType": "origin-request",
- "IncludeBody": false,
+ "EventType": "origin-response",
"LambdaFunctionARN": "arn:aws:lambda:us-east-1:redacted"
}
]
Metadata
Metadata
Assignees
Labels
This issue/PR relates to a bugGood for new comers and easy to start with contributionmoduleThis issue requires further information. Please answer any outstanding questionsThis issue/PR has an incomplete description. Please fill in the proposed template correctlyplugin (any type)Needs help. Feel free to engage to get things unblocked