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.

Pulumi Community

I've just updated kubernetes from 1.1.0 to 1.2.1 and it wants to redeploy every configmap (from using binaryData property to data) and thus redeploy everything that uses those config maps.
is that expected? will it actually redeploy things?

Can you get the details of what the `pulumi up` is suggesting it will change?

`pulumi up` then choose details, grab the output and then say no to the prompt

Resources:
    ~ 7 to update
    +-76 to replace
    83 changes. 64 unchanged

7 configmaps to update, 76 dependent resources to replace

hm in the 'details' it looks different to update --diff

~ kubernetes:core/v1:ConfigMap: (update)
        [id=logging/gf3-appsettings-event-forwarder-4a2a140f]
        [urn=urn:pulumi:dev1-apps-gf3::dev1-apps-gf3::kubernetes:core/v1:ConfigMap::gf3-appsettings-event-forwarder]
        [provider=urn:pulumi:dev1-apps-gf3::dev1-apps-gf3::pulumi:providers:kubernetes::dev1::c6d4e8be-55aa-4475-a4aa-334b72786b84]
      ~ metadata: {
          ~ annotations: {
              + <http://pulumi.com/initialApiVersion|pulumi.com/initialApiVersion>: "v1"
            }
        }

seems to be just an annotation for that one

<@UCZGDUBDJ> we’re fixing this cc <@UE1LN7A22>

FYI, removing the `initialApiVersion` annotation as it’s causing unnecessary churn - <https://github.com/pulumi/pulumi-kubernetes/pull/837>

<@UCZGDUBDJ> does adding any annotation cause replacement? is there anything else in the diff?

i think it's just annotations and the binaryData / data thing is unrelated

i'll wait for that update levi mentioned, cheers!

great that's fixed everything, no changes now. thanks a lot.