[bitnami/wordpress] Document values that are not changed on upgrades

[madalinignisca]

Name and Version

bitnami/wordpress 15.2.45

What steps will reproduce the bug?

1. Using Helm3 I installed WordPress with a custom values.yml file.
2. Tested and all worked well.
3. Later I decided to add a certain plugin that requires adding to wp-config.php some snippet of code.
4. I added to values.yml the wordpressExtraConfigContent with the additional configuration.
5. I run helm with upgrade of release using the values.yml file

Are you using any custom parameters or values?

added after initial install wordpressExtraConfigContent with required extra wordpress configuration

What is the expected behavior?

I expected wp-config.php to have the additional configuration added to the file

What do you see instead?

wp-config.php has not changed at all.

Additional information

I thought that wp-config.php would be generated on pod's deployment as tweaking the wordpress configuration from helm's overriding values would make sense.

The container doesn't contain not even a basic editor like vi or nano to allow manually changing the wp-config.php file later.

Sidenote, changing some other stuff in values.yml and redeploying using helm did change other things as expected (tweaking mariadb's config for example did work)

[madalinignisca]

I found an issue on similar topic, which is closed but with no news on the internal task that was opened about the same property not working: #10329 (comment)

I guess the intended wordpressExtraConfigContent is completely ignored on upgrades of the deployment.

[madalinignisca]

Another previous issue on same topic highlighted what I pointed previously that on redeploying configuration will not be altered.

#7120 (comment)

For us the users, this is the exact opposite expectation from a HELM deployed application.

All popular HELM applications (Nginx Ingress, Cert Manager, Cillium etc.) change their configuration on overriding values.yml.

Bitnami's internal decision on web apps to lock config after first install is unexpected for HELM users and opposite of the common pattern that HELM apps work.

[madalinignisca]

Please in all web applications document properties from values.yml that will only have effect on install and none on upgrades. I assume that there are many more for all web applications in the Bitnami Charts. And ideally, configuration must have an easy way to be edited later, so at least vi or nano should be included in the container image.

[javsalgar]

Hi,

Thank you so much for the feedback! I will forward this to the documentation team. I'm afraid I cannot guarantee an ETA, but if you want to speed up the process, feel free to submit a PR and we will take a look.

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

[Preen]

Why was this closed/solved as not planned??