search

bitnami / charts

Bitnami Helm Charts
https://bitnami.com
Other
8.92k stars 9.18k forks source link

JasperReports - Upload a jar file for each connection type that isnt installed #12320

Closed chrispward closed 2 years ago

chrispward commented 2 years ago

Name and Version

JasperReports:Latest

What is the problem this feature will solve?

More of a question of can we do it... if not then we need a feature request...

The bitnami docker image only comes with 2 jdbc database connectors installed. (postgress and msql) This is for a report/dashboards etc to be able to query from.

The other common ones like Oracle/sqlserver, teradata etc are not installed. To install them, you have to upload the jdbc .jar for each provider to the /opt/bitnami/tomcat/lib directory and restart the server. ie https://community.jaspersoft.com/wiki/connecting-jasperreports-server-your-database

As a test, I was able to manually upload the teradata.jar file, but I cant seem to restart the server. ie kubectl cp /data/software/terajdbc4.jar jasper-jasperreports-768bd9b9b7-dx4zl:/opt/bitnami/tomcat/lib -n jasper if I try exec'ing into pod and running /opt/bitnami/scripts/tomcat/restart.sh it just runs a new java instance and doesnt stop the old one. This is a workaround anyway as a test.

The real question/way to do it.. is to upload the jar(s) file somehow and install them in the /lib before the server starts running.

(i'm trying to avoid having to build my own docker image which is another approach .. but you'd have to do that for every connection type/change etc which would be cumbersome).

Anyway, can upload a jar file and use an init function or something?

What is the feature you are proposing to solve the problem?

Some way to upload a jar file and restart the server or upload it before the server starts

What alternatives have you considered?

i'm trying to avoid having to build my own docker image which is another approach .. but you'd have to do that for every connection type/change etc which would be cumbersome

javsalgar commented 2 years ago

Hi,

Please, note this Helm chart is a community-supported solution. This means that the Bitnami team is not actively working on new features/improvements nor providing support through GitHub Issues for this Helm chart. Any new issue will stay open for 20 days to allow the community to contribute, after 15 days without activity the issue will be marked as stale being closed after 5 days.

The Bitnami team will review any PR that is created, feel free to create a PR if you find any issue or want to implement a new feature.

New versions are not going to be affected. Once a new version is released in the upstream project, the Bitnami container image will be updated to use the latest version.

bitnami-bot commented 2 years ago

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.

bitnami-bot commented 2 years ago

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.