feat: Add Helm configMap to update application configuration

[geekup-legodevops]

Description

• Adding Helm ConfigMap for users who deploy Appsmith by Helm Chart to change application configuration
• Refactor the flow that being used to generate environment variables for supporting predefined environment variables when initializing the container

Type of change

• New feature (non-breaking change which adds functionality)

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[vercel]

@geekup-legodevops is attempting to deploy a commit to the Appsmith Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

This PR has not seen activitiy for a while. It will be closed in 7 days unless further activity is detected.

[sharat87]

Looks much better, thanks guys. Just a couple of minor questions, otherwise we are ready to merge this in!

[WernerEngelsB]

Hi all,
seems to me, this line, does not work as expcected on our kubernetes 1.21 environment.
only default-env-vars from $ENV_PATH are actually used within the script, following "pre-define.env"-files are not picked up, even though the file exists and contains values (e.g. for mongo-db).

See attached screenshot, where I entered some debugging points to point out env-variables while running entrypoint.sh:

[WernerEngelsB]

@sharat87 could you have a look at this?

[sharat87]

Hey, while I'm not sure of this without looking at the entrypoint_wdr.sh script, I think you are dealing with the issue fixed in this PR: #11799. We should be publishing it soon.

As a workaround in the meantime, could you try adding a backslash just before the ? and see if that makes a difference?

[WernerEngelsB]

@sharat87 Thank you for pointing out #11799 to me. Actually escaping Question-Marks (?) and Ampersands (&) with a backslash (or in my case double back-slash to get it through our own scripting-pipeline) worked for me. Looking forward to the PR to be released, as other special-chars might be problematic as well (as described in the PR)
Thank you