eks cluster certificate authority breaking change

Hello!

• 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)

Issue details

Trying to renovate pulumi-aws from 4.38.1 to 5.1.0 hits a breaking change in the dotnet sdk where Cluster.CertificateAuthority was renamed and retyped to array Cluster.CertificateAuthorities.

I fixed the build by updating the signatures but then this fails to deploy to an existing cluster, presumably since this change is not reflected in the existing state:

Diagnostics:
  pulumi:pulumi:Stack (aws-eks-test):
    error: Running program '' failed with an unhandled exception:
    System.NullReferenceException: Object reference not set to an instance of an object.
       at T System.Collections.Immutable.ImmutableArray<T>.get_Item(int index)
       at Pulumi.Dungeon.Aws.EksStack(IOptions<Config> options, ILogger<EksStack> logger)+(ImmutableArray<ClusterCertificateAuthority> authorities) => { }
       at Output<U> Pulumi.Output<T>.Apply<U>(Func<T, U> func)+(T t) => { }
       at async Task<OutputData<U>> Pulumi.Output<T>.ApplyHelperAsync<U>(Task<OutputData<T>> dataTask, Func<T, Output<U>> func)
       at async Task<OutputData<ValueTuple<T1, T2, T3, T4, T5, T6, T7, ValueTuple<T8>>>> Pulumi.Output<T>.TupleHelperAsync<T1, T2, T3, T4, T5, T6, T7, T8>(Input<T1> item1, Input<T2> item2, Input<T3> item3, Input<T4> item4, Input<T5> item5, Input<T6> item6, Input<T7> item7, Input<T8> item8)+GetData(?)
       at async Task<OutputData<ValueTuple<T1, T2, T3, T4, T5, T6, T7, ValueTuple<T8>>>> Pulumi.Output<T>.TupleHelperAsync<T1, T2, T3, T4, T5, T6, T7, T8>(Input<T1> item1, Input<T2> item2, Input<T3> item3, Input<T4> item4, Input<T5> item5, Input<T6> item6, Input<T7> item7, Input<T8> item8)
       at async Task<OutputData<U>> Pulumi.Output<T>.ApplyHelperAsync<U>(Task<OutputData<T>> dataTask, Func<T, Output<U>> func) x 3

I’m not sure whether or not this is something pulumi should be fixing on their end, and if not, what needs to be done to fix the deploy to an existing environment created with the pre 5.x version of pulumi aws?

[stack72]

Hi @gitfool

I have just mardked this as a P1 and will have a fix out for this today to ensure that both types can be used

Paul

[gitfool]

Confirmed this is now backwards compatible in pulumi-aws 5.1.2. 🚀