The nident in the airflow chart is incorrect inside of the setup db job

[samuel-davis]

Name and Version

bitnami/airflow 22.4.3

What architecture are you using?

None

What steps will reproduce the bug?

Attempt to change the resources for the setupDbJob to anything other than a preset.

Are you using any custom parameters or values?

No just default resources.

What is the expected behavior?

That the pod is configured.

What do you see instead?

  install.go:241: 2025-01-10 12:46:21.823244748 -0500 EST m=+1.768469185 [debug] CHART PATH: /home/sam/.cache/helm/repository/airflow-22.4.3.tgz
  Error: YAML parse error on airflow/templates/setup-db-job.yaml: error converting YAML to JSON: yaml: line 139: mapping values are not allowed in this context
  helm.go:86: 2025-01-10 12:46:21.879415546 -0500 EST m=+1.824639998 [debug] error converting YAML to JSON: yaml: line 139: mapping values are not allowed in this context

Additional information

charts/bitnami/airflow/templates/setup-db-job.yaml

Line 49 in d1a8d92

resources: {{- toYaml .Values.setupDBJob.resources | nindent 4 }}

Line 49 of the setup-db-job.yaml should be changed from

          resources: {{- toYaml .Values.setupDBJob.resources | nindent 4 }}

to

          resources: {{- toYaml .Values.setupDBJob.resources | nindent 12 }}

[carrodher]

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

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