ebsan / generator-jhipster-es-entity-reindexer Goto Github PK

We should be able to add Application properties for reindex-on-startup to application.yml without rewriting the whole file. There is no jhipster needle for it but alternative is dicussed in jhipster/generator-jhipster#17838.

Version 1.0.2
JHipster 7.9.3

During the installation of the generator, the application.yml looks to have received several changes that were unintended.

Specifically:

1. Removal of management:env:enabled:true
2. spring:application:name is updated to AndroidSoftwarePortal
3. spring:main:allow-circular-references:true is set (possibly intentional, but no documented explanation 🤔 )
4. spring:task:execution:thread-name-prefix is updated to android-software-portal-task-
5. spring:task:scheduling:thread-name-prefix is updated to android-software-portal-scheduling-
6. spring:security:oauth2 is removed (somewhat alarming)
7. jhipster:clientApp:name is updated to androidSoftwarePortalApp
8. jhipster:api-docs:{title,description} are updated to Android Software Portal API and Android Software Portal API documentation, respectively
9. jhipster:security:content-security-policy is updated (omitted for brevity)
10. jhipster:security:oauth2 is removed (somewhat alarming, but possibly an artifact of a missing EOF line feed and Git behaviors)

I reverted these changes, leaving only application:elasticsearch:reindex-on-startup:true

Using Jhipster 7.9.3 when I generate a standard gateway and basic entity and chose "react" instead of angular as client framework the reindexer will not work and gives the following error

When creating a standard reactive microservice with a basic entity when the reindex is run the resulting generated ElasticsearchIndexService class tries to use jpaRepository instead of R2dbcRepository and contains compile errors.

Jhipster version: 7.9.3
node version: v16.13.0
npm version: 8.1.0

gateway_yo.json.txt
microservice_yo.json.txt

Version 1.0.2
JHipster 7.9.3

Installed per instructions, npm install -g generator-jhipster-es-entity-reindexer then followed with yo jhipster-es-entity-reindexer

Classes were placed in /src/main/java/undefined/{config,web/rest,service}:

% pwd 
~/Development/monolith/src/main/java/undefined
% ls **/*
config/ApplicationProperties.java        service/ElasticsearchIndexService.java   web/rest/ElasticsearchIndexResource.java

config:
ApplicationProperties.java

service:
ElasticsearchIndexService.java

web:
rest

web/rest:
ElasticsearchIndexResource.java

Previous versions allowed an environment variable set by the user to reindex all entities. Another way to do it would be to add a Application Specific property for the ApplicationProperties class. There may be more ways to do this so we need to investigate.

The original module handled Jhipster applications that skipped frontend or backend parts of the app (https://www.jhipster.tech/separating-front-end-and-api/).