We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For example, if we add the following configuration:
quarkus.datasource.jdbc.url=${POSTGRESQL_URL} quarkus.datasource.username=${POSTGRESQL_USERNAME} quarkus.datasource.password=${POSTGRESQL_PASSWORD}
I would like that the Quarkus HELM extension to automatically map those values into the generated Values.yaml file as:
app: envs: POSTGRESQL_URL: POSTGRESQL_USERNAME: POSTGRESQL_PASSWORD:
At the moment, the only workaround is to configure either Kubernetes or Openshift as follows:
quarkus.openshift.env.vars.POSTGRESQL_URL=jdbc:postgresql://host:1111/database quarkus.openshift.env.vars.POSTGRESQL_USERNAME=user quarkus.openshift.env.vars.POSTGRESQL_PASSWORD=pass
And now, the Quarkus Helm will map those values.
It would be great if we could automatically find the system properties without needing to configure quarkus.openshift.env.vars.xxx.
quarkus.openshift.env.vars.xxx
The text was updated successfully, but these errors were encountered:
Automatically map system properties as container env vars
e93ce75
Fix #177
2e12f8d
Successfully merging a pull request may close this issue.
For example, if we add the following configuration:
I would like that the Quarkus HELM extension to automatically map those values into the generated Values.yaml file as:
At the moment, the only workaround is to configure either Kubernetes or Openshift as follows:
And now, the Quarkus Helm will map those values.
It would be great if we could automatically find the system properties without needing to configure
quarkus.openshift.env.vars.xxx
.The text was updated successfully, but these errors were encountered: