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

You can use a transformation to modify the existing config map, or drop it from the chart and using a transformation and just add your own resource instead 

What file are you trying to override? Most Helm charts (all?) provide a `values.yaml` replacement option which Pulumi supports providing.

You need to investigate this `values.yaml` , figure out what config you need to change, and then create teh pulumi `values: {}` comparable object in your Chart options.

<https://github.com/bitnami/charts/blob/master/bitnami/phpmyadmin/values.yaml>

<@UMW5G5Z6D> that variable isn't in the values.yaml, it's a setting in `php.ini`

That's sucks. Does the container allow for setting a volume that you can put your own php.ini in?

I have zero experience with that particular bitnami chart, so I'm just spitballing ideas here! :smile:

<@U014YTFPGAU> it appears you can set the maxupload size using `PHP_UPLOAD_MAX_FILESIZE` as an environment variable. The chart doesn't appear to support arbitrary env vars, but you can use a transform to set it. Let me know if you'd like an example

Thanks everyone, trying this out now:
```    transformations: [
      (obj: any) =&gt; {
        if (obj.kind === 'Deployment') {
          obj.spec.template.spec.containers[0].env.push({
            name: 'PHP_UPLOAD_MAX_FILESIZE',
            value: '1G',
          });
          console.log(JSON.stringify(obj, null, 2));
        }
      },
    ],```

(transformations are my favourite pulumi feature)

It adds the vars but doesn't fix my problem. Maybe it's defined in multiple places