[bitnami/airflow] Add dag volume mounts to web deployment for configmap-based dags

[TheRobotCarlson]

Description of the change

When using configmap-based DAGs, the DAGs are not linked to the webapp correctly, leading to them not being properly loaded in the UI. This PR adds them and the init containers that sync them to the necessary volume and volume locations.

Benefits

Possible drawbacks

Applicable issues

• fixes #

Additional information

Checklist

• Chart version bumped in Chart.yaml according to semver. This is not necessary when the changes only affect README.md files.
• Variables are documented in the values.yaml and added to the README.md using readme-generator-for-helm
• Title of the pull request follows this pattern [bitnami/<name_of_the_chart>] Descriptive title
• All commits signed off and in agreement of Developer Certificate of Origin (DCO)

[dgomezleon]

LGTM. Thanks for contributing

[dgomezleon]

Hi @TheRobotCarlson ,

We needed to apply this change to make it work with our tests. Could you please rebase it? Also, you would need to add the syncDags sidecar container.

[TheRobotCarlson]

Hi @dgomezleon, I've rebased. The sync-dags init container isn't needed for configmap-based deployments, is it? Since it is responsible for syncing git repos and not configmaps?

[juan131]

Hi @dgomezleon, I've rebased. The sync-dags init container isn't needed for configmap-based deployments, is it? Since it is responsible for syncing git repos and not configmaps?

Correct, but you're adding a generic solution that should be valid for both obtaining DAGs from an existing ConfigMaps OR cloning a repository with them.

[TheRobotCarlson]

@juan131 Does this mean the git-based DAG loading flow is not being tested at all? This would mean neither configmap-based or git-based DAG flows are working from the default deployment. I have been testing configmap-based deployments and don't have a git-based deployment flow to test from currently.