Closed omidraha closed 3 months ago
iwahbe
commented
7 months ago Hi @omidraha. Thanks for opening an issue. We're sorry to hear about this. To help us diagnose the problem, can you please post the output of pulumi about in the issue. In this case, we want to know the version of pulumi and the version of pulumi-aws that you are using so we can reproduce the bug on our machines.
omidraha
commented
7 months ago @iwahbe , I just have updated for pulumi about.
iwahbe
commented
7 months ago This is a superset of https://github.com/pulumi/pulumi-aws/issues/3190.
t0yv0
commented
4 months ago Apologies, this is still a problem. Adding some technical notes here
Still reproduces after all the fixes:
~ rules: [
~ [0]: {
~ action : {
+ __defaults: []
~ count : {
+ __defaults: []
}
}
~ name : "waf-rule-group-argfoo" => "waf-rule-group-argfoo"
~ priority : 1 => 1
~ statement : {
+ __defaults : []
~ rateBasedStatement: {
+ __defaults : [
+ [0]: "evaluationWindowSec"
]
aggregateKeyType : "IP"
- customKeys : []
evaluationWindowSec: 300
limit : 100
}
}
~ visibilityConfig: {
+ __defaults : []
cloudwatchMetricsEnabled: true
metricName : "WafRbrFooMetric"
sampledRequestsEnabled : true
}
}
]
The problem is that - customKeys : [] is cycling between empty list and nil/missing. This is compounded by getting confused about the set element identity and improper set diff display.
Superficially looks very similar to https://github.com/pulumi/pulumi-terraform-bridge/pull/1917 so possibly the same root cause and same work-around apply.
What happened?
I tried to create a
wafwith rate limit rule, Thewafandwaf groupresources created but when I runpulumi upI always getdiff updatefor it.Example
Here is the source code to reproduce it:
Info:
Info
Output of
pulumi aboutAdditional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).