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

Hi,

Don't use the secret generation inside the Helm chart. Create the secret beforehand (via Pulumi Secret resource) and pass the secret to the Datadog Helm Chart (look for values like `existingSecret` or `secretRef`)

Hmm I don’t care about this secret (it’s for DD internal communication) and I believe DD Helm chart does its own secret rotation. It’s counter-intuitive to generate my own for something internal to DD

FYI I believe one of the recommended way is to use `ignoreChanges` in this document: <https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/#handle-field-conflicts-on-existing-resources|https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/#handle-field-confl[…]existing-resources>

You can drop the secret entirely using a transformation. There’s an example of that in the API docs: <https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm/v3/chart/#chart-with-transformations>