This message was deleted.

sparse-intern-71089

06/30/2021, 7:04 PM

This message was deleted.

billowy-army-68599

06/30/2021, 7:07 PM

Sorry you’re hitting this, I think this warrants a bug report, would you mind filing an issue?

gentle-diamond-70147

06/30/2021, 7:07 PM

As jaxxstorm said, this sounds like a bug. As a workaround, can you try adding

ignoreChanges: ["properties.nodeTaints"]

(or the correct resource property name) to see if Pulumi will ignore those and allow the update to proceed?

dazzling-alarm-77720

06/30/2021, 7:11 PM

Adding ignoreChanges: [ "nodeTaints" ] didn't work, but adding "count" (which is what was causing the stack to currently think it needed to update the resource) did prevent Pulumi from trying to update the agent pool and failing.

dazzling-alarm-77720

06/30/2021, 7:12 PM

But if we ever want to change the maxCount/etc. we will hit this again unless we also ignore changes on those properties..

gentle-diamond-70147

06/30/2021, 7:18 PM

Understood. That's meant as a workaround for now to hopefully "unstick" you.

gentle-diamond-70147

06/30/2021, 7:19 PM

Could you open an issue at https://github.com/pulumi/pulumi-azure-native with the code and steps to reproduce this?

stale-autumn-24797

06/30/2021, 7:21 PM

Pulumi update issues with AKS clusters · Issue #959 · pulumi/pulumi-azure-native (github.com )

stale-autumn-24797

06/30/2021, 7:22 PM

Put both issues in the same bug. You can split them if needed.

gentle-diamond-70147

06/30/2021, 7:22 PM

Thank you. I will chat with some people internally.

6 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.