Marcelo Shima
Marcelo Shima
I don't get why the application does not fails in some containers failures: ``` [0] Error starting ApplicationContext. To display the condition evaluation report re-run your application with 'debug' enabled....
- container integration workflow is conditional to `pr: docker-compose integration` label - container integration workflow can have false positives - we need to add a strong password to PostgreSQL to...
> Is there an issue detailing why Keycloak doesn't work? https://github.com/spring-projects/spring-boot/issues/36777
> When I first heard about this feature, I remember seeing it was possible to point at our existing Docker Compose files, which don't use testcontainers. Can we do that...
> It still has an eslint warning too: > > ``` > npm warn ERESOLVE overriding peer dependency > npm warn While resolving: [email protected] > npm warn Found: [email protected] >...
> Lots of logging happens at the beginning, probably unrelated to this branch. Fixed in https://github.com/jhipster/generator-jhipster/pull/27267
> This might help: [mshima#1010](https://github.com/mshima/generator-jhipster/pull/1010) @mraible that config is already provided in application.yml
> > v8.7.0 release is installed. > > I don't think so. I'm pulling from your `compose` branch, running `npm ci` and `npm link` before I run `jhipster`. I tried...
> > that config is already provided in application.yml > > Shouldn't it be in application-dev.yml since it's only needed when using the dev profile? It should work using prod...
@mraible see 2 latest commits for service discovery. But seems to have a dependency problem now.