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

after finding <https://pulumi.io/reference/programming-model.html#programming-model> i think i get it some of it, regarding how the configmap name is referenced — but still missing the part about create new + replace old

<@UCRRFL4TB> so, there are a subset of fields in `ConfigMap` that, when changed, trigger us to replace-then-delete

These aren’t written down in the docs anywhere, but we probably shoult.

Basically the semantics are: if you change anything in the `data` field, we will create a new configmap with the updated data, update all objects referencing it, and then delete the old one, after success.

<@UCRRFL4TB> I’ll file a bug to write docs about this.

filed: <https://github.com/pulumi/pulumi-kubernetes/issues/211> <https://github.com/pulumi/pulumi-kubernetes/issues/212>