[bitnami/wordpress] Injecting extra config into wp-config.php

[v1nc3nt27]

Name and Version

bitnami/wordpress 19.1.2 helm chart

What architecture are you using?

amd64

What steps will reproduce the bug?

I use the latest helm chart 19.1.2 and I want to inject extra config via wordpressExtraConfigContent

wordpressExtraConfigContent: |
  define('WP_ALLOW_REPAIR', true);

I saw #21616 and I was wondering if there is any setup that allows wordpressExtraConfigContent to work or is it buggy at the moment?

Are you using any custom parameters or values?

wordpressSkipInstall: true 
wordpressExtraConfigContent: |
  define('WP_ALLOW_REPAIR', true);

What is the expected behavior?

I expect that the additional config is added to wp-config.php

What do you see instead?

Nothing is added.

[rafariossaa]

Are you upgrading or installing from scratch ?
I am asking because WORDPRESS_EXTRA_WP_CONFIG_CONTENT is only used the first time when it is being installed.

[v1nc3nt27]

Hm, I am migrating from a different host. But only my database is already cloned, the installation is clean, so I'd say it is an installation from scratch. The idea is to use a backup tool after installation is done to migrate the content.

[rafariossaa]

Could you paste the PODs logs and the command you are using to deploy it ?

[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.