Generated project dont include the proper application.properties & import.sql

[cmoulliard]

Issue

When we generate a project using the option starter=true with code.quarkus.io, then the generated project don't include:

• application.properties

  
  {% if values.database == 'quarkus-jdbc-postgresql' %}
  # Kubernetes Service name to access the DB should be as defined within the helm chart => postgresql:5432
  # apiVersion: v1
  # kind: Service
  # metadata:
  #  name: {{ include "postgresql.primary.fullname" . }}
  #  see: https://github.com/bitnami/charts/blob/9ba6ba51cf7c094e457396c423f5843df46023a2/bitnami/postgresql/templates/primary/svc.yaml#L4
  %prod.quarkus.datasource.jdbc.url=jdbc:postgresql://${{ values.database_name }}-postgresql:5432/${{ values.database_name }}
  %prod.quarkus.datasource.username=${{ values.database_username }}
  {% elif values.database == 'quarkus-jdbc-mysql' %}
  %prod.quarkus.datasource.jdbc.url=jdbc:postgresql://${{ values.component_id }}-db:3306/${{values.component_id}}-db
  %prod.quarkus.datasource.username=root
  {% elif values.database == 'quarkus-jdbc-h2' %}
  %prod.quarkus.datasource.db-kind=h2
  %prod.quarkus.datasource.jdbc.url=jdbc:h2:mem:quarkus
  {% endif %}

%prod.quarkus.hibernate-orm.sql-load-script=import.sql %prod.quarkus.hibernate-orm.database.generation=drop-and-create

- import.sql file matching the entity

-- This file allow to write SQL commands that will be emitted in test and dev. insert into myentity (id, field) values(1, 'field-1'); insert into myentity (id, field) values(2, 'field-2'); insert into myentity (id, field) values(3, 'field-3'); alter sequence myentity_seq restart with 4;

![Screenshot 2024-04-17 at 10 05 08](https://github.com/q-shift/qshift-templates/assets/463790/83f87e93-2d85-420c-9e5d-8fcc8e231fac)

Query: `https://code.quarkus.io/?e=rest&e=hibernate-orm-rest-data-panache&e=jdbc-postgresql&extension-search=postgres`

[cmoulliard]

I think we should keep in our backstage template the generation of the content of "application.properties" with the database properties (postgresql, h2, etc) + username and db

I'm more skeptical about the import.sql file because we are dependent on what code.quarkus.io generates and that could change if the Entity name change over the time

@aureamunoz WDYT ?

[aureamunoz]

Yes, I think it would be easier to managed and quicker to craft if we need modifications and tailored features

[cmoulliard]

Soon, we will add primaza to resolve such issue ;-)