Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bitnami/apisix] JSONSchema too strict for extraEnvVars #27319

Closed
james-mchugh opened this issue Jun 17, 2024 · 6 comments · Fixed by #27441
Closed

[bitnami/apisix] JSONSchema too strict for extraEnvVars #27319

james-mchugh opened this issue Jun 17, 2024 · 6 comments · Fixed by #27441
Assignees
Labels
apisix solved tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@james-mchugh
Copy link
Contributor

james-mchugh commented Jun 17, 2024

Name and Version

bitnami/apisix:3.1.2

What architecture are you using?

amd64

What steps will reproduce the bug?

  1. Set .Values.dataPlane.extraEnvVars to a string (containing Helm templating, for example)
  2. Run helm template .
  3. Observe error due to JSON schema validation

Are you using any custom parameters or values?

dataPlane:
  extraEnvVars: |-
      {{- include "my-chart.apisix.authEnvs" . }}

What is the expected behavior?

dataPlane.extraEnvVars allows for strings as the value is passed to the common.tplvalues.render template function prior to being added to the deployment/daemonset.

What do you see instead?

Error: INSTALLATION FAILED: values don't meet the specifications of the schema(s) in the following chart(s):
apisix:
- dataPlane.extraEnvVars: Invalid type. Expected: array, given: string

Additional information

There may be additional fields with similar issues.

I took a look at the Bitnami Postgresql chart, which omits extraEnvVars fields from the JSON schema. Other charts may handle this differently though.

@james-mchugh james-mchugh added the tech-issues The user has a technical issue about an application label Jun 17, 2024
@github-actions github-actions bot added the triage Triage is needed label Jun 17, 2024
@carrodher
Copy link
Member

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.

@james-mchugh
Copy link
Contributor Author

Sure thing. I can put a PR together for this.

@james-mchugh
Copy link
Contributor Author

PR opened!

@carrodher
Copy link
Member

Thank you for opening this issue and submitting the associated Pull Request. Our team will review and provide feedback. Once the PR is merged, the issue will automatically close.

Your contribution is greatly appreciated!

@james-mchugh
Copy link
Contributor Author

Hello @carrodher . Sorry to bug you about this, but do you have a timeline for when the PR might be reviewed by? I'm more than happy to reduce the changes if that will help with the review. I'm just hoping to not have to continue forking the chart for too long to get around a simple JSON schema validation issue.

@carrodher
Copy link
Member

Hi @james-mchugh, thank you for your contribution! We truly appreciate your effort and interest in improving the bitnami/apisix chart.

Our team currently has a high volume of Issues and Pull Requests to review. Please be assured that we are doing our best to get to yours as soon as possible. We appreciate your patience and understanding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
apisix solved tech-issues The user has a technical issue about an application triage Triage is needed
Projects
None yet
2 participants