smallrye-health | : microprofile-health : https : //github | Microservice library

I have a quarkus project I try to secure some of my endpoints with a Jwt token.

So far, it don't work. everything is still accessible.

my application.properties:

I have a Quarkus project that expose some REST Endpoints. When working on dev mode or running from the local build docker container all work fine, those endpoints annotated with @RolesAllowed and @PermitAll work as supposed to be. But when I deploy to a AWS service with the following steps:

1. Commit to Gitlab
2. Run Gitlab CICD
3. Send result with the config to an AWS S3 Bucket
4. Trigger AWS codepipeline
5. Deploy to Elastic Bean using docker image

After that the container is deployed all endpoints with @PermitAll work fine but those with @RolesAllowed responds with 401 Unauthorized, the token sent to those endpoints is valid, it is correctly formed and has not expired.

I started a project and have about 7 tests in my project now and it takes already more than a minute to execute the whole test suite using gradle test.

From the additional output (--info flag) I can see that the whole quarkus application and also dependencies like the mongodb instance are restarted for every test class and method.

This is the exact opposite of what the quarkus documentation says on the testing guide page:

So far in all our examples we only start Quarkus once for all tests. Before the first test is run Quarkus will boot, then all tests will run, then Quarkus will shutdown at the end. This makes for a very fast testing experience however it is a bit limited as you can’t test different configurations.

All the tests are annotated with @QuarkusTest and every test just tests a single endpoint.

I use "pure" kotlin (1.5.21), Quarkus version 2.2.2.Final and gradle 6.9. Installed features: cdi, config-yaml, jacoco, kotlin, mongodb-client, mongodb-panache-kotlin, narayana-jta, rest-client, rest-client-jackson, resteasy, resteasy-jackson, smallrye-context-propagation, smallrye-health, smallrye-openapi, swagger-ui

Is that a normal behaviour? If yes, an application with multiple hundred tests could easily take ~20 minutes or more to run the entire test suite.

I didn't try out maven yet, so I can't verify that it's not a gradle related issue.

After upgrading from Quarkus 1.11.3.Final to 2.2.3.Final my Unittests are failing with following message: Caused by: java.lang.IllegalStateException: Invalid use of io.quarkus.test.junit.mockito.InjectMock - the injected bean does not declare a CDI normal scope but: javax.inject.Singleton. Offending field is cloudEventPublisherMock of test class class ch.zhaw.ba.services.order.MyTest

This is the offending class behind the field, clearly annotated with @ApplicationScoped (not Singleton):

I'm trying to deploy a Quarkus app to a Kubernetes cluster, but I got the following stacktrace:

I'm trying to run Quarkus from my local machine (windows). It works. However, when I go to the landing page, it does not serve swagger.

The log shows:

I am trying to get Debezium to send my CDC events to Kinesis and the service seems to start but there are errors, and it doesn't seem to be sending anything to Kinesis. I was following this setup guide on the Debezium site:

https://debezium.io/documentation/reference/1.2/operations/debezium-server.html

Here is my config file:

Occurs when running on IntelliJ IDE 2019.3.4 with JDK GraalVM 20.0.0 and maven 3.6.3.