Open t0yv0 opened 1 year ago
On V6 this stack has a similar but different problem:
Do you want to perform this refresh?
No resources will be modified as part of this refresh; just your stack's state will be.
details
pulumi:pulumi:Stack: (same)
[urn=urn:pulumi:eksdebug::resources::pulumi:pulumi:Stack::resources-eksdebug]
~ aws:iam/role:Role: (update)
[id=ekscluster1role-3d947ce]
[urn=urn:pulumi:eksdebug::resources::aws:iam/role:Role::ekscluster1role]
[provider=urn:pulumi:eksdebug::resources::pulumi:providers:aws::provider::72b09d72-d11c-41e8-9c98-b0557ce66591]
--outputs:--
- roleLastUseds : [
- [0]: {
- lastUsedDate: ""
- region : ""
}
]
~ aws:ec2/vpc:Vpc: (update)
[id=vpc-0d04740861cf1d0f6]
[urn=urn:pulumi:eksdebug::resources::aws:ec2/vpc:Vpc::vpc1]
[provider=urn:pulumi:eksdebug::resources::pulumi:providers:aws::provider::72b09d72-d11c-41e8-9c98-b0557ce66591]
--outputs:--
- enableClassiclink : false
- enableClassiclinkDnsSupport : false
Do you want to perform this refresh?
No resources will be modified as part of this refresh; just your stack's state will be.
[Use arrows to move, type to filter]
yes
Using
provider:
type: pulumi:providers:aws
options:
version: 6.0.2-alpha.2+9b14ba69
Still a problem:
Previewing refresh (repro2)
View in Browser (Ctrl+O): https://app.pulumi.com/anton-pulumi-corp/resources/repro2/previews/22ff7902-cbf3-4dbd-916d-cd889bc19484
Type Name Plan Info
pulumi:pulumi:Stack resources-repro2
├─ pulumi:providers:aws provider
~ ├─ aws:iam:Role ekscluster1role update [diff: ~managedPolicyArns]
├─ aws:iam:RolePolicyAttachment ekscluster1roleattach2
├─ aws:ec2:Subnet subnet1
├─ aws:iam:RolePolicyAttachment ekscluster1roleattach1
├─ aws:ec2:Subnet subnet2
├─ aws:ec2:Vpc vpc1
~ └─ aws:eks:Cluster ekscluster1 update [diff: +defaultAddonsToRemoves]
Resources:
~ 2 to update
7 unchanged
Do you want to perform this refresh?
No resources will be modified as part of this refresh; just your stack's state will be.
details
pulumi:pulumi:Stack: (same)
[urn=urn:pulumi:repro2::resources::pulumi:pulumi:Stack::resources-repro2]
~ aws:iam/role:Role: (update)
[id=ekscluster1role-1c24246]
[urn=urn:pulumi:repro2::resources::aws:iam/role:Role::ekscluster1role]
[provider=urn:pulumi:repro2::resources::pulumi:providers:aws::provider::9ac84da1-b67e-4670-856e-1ad436474fac]
--outputs:--
~ managedPolicyArns : [
+ [0]: "arn:aws:iam::aws:policy/AmazonEKSClusterPolicy"
+ [1]: "arn:aws:iam::aws:policy/AmazonEKSVPCResourceController"
]
~ aws:eks/cluster:Cluster: (update)
[id=ekscluster1-421a7c7]
[urn=urn:pulumi:repro2::resources::aws:eks/cluster:Cluster::ekscluster1]
[provider=urn:pulumi:repro2::resources::pulumi:providers:aws::provider::9ac84da1-b67e-4670-856e-1ad436474fac]
--outputs:--
+ defaultAddonsToRemoves : []
The problem is self-correcting after refresh. Looks like Read is normalizing defaultAddonsToRemoves from missing to []
.
"default_addons_to_remove": {
Type: schema.TypeList,
Optional: true,
Elem: &schema.Schema{
Type: schema.TypeString,
},
}
managedPolicyArns is exactly the same as in https://github.com/pulumi/pulumi-aws/issues/2246
What happened?
Unexpected update plan for a refresh right after pulumi up:
Expected Behavior
Refreshing eks.Cluster that was just provisioned does not generate update plans.
Steps to reproduce
Steps:
Output of
pulumi about
Additional context
This issue was discovered as part of building out provider upgrade tests and surfaced when recording baseline provider behavior for the eks.Cluster resource.
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).