any reason root-path can't be runtime?

[William Burke]

Is there any reason quarkus.http.root-path has to be fixed at build time and cannot be set by an ENV VAR?    A user ran into an issue with AWS Gateway deployment stages.  Seems that the deployment stage name changes the root path.  They have to recompile their apps when they change the stage.

--

Bill Burke

Red Hat

[William Burke]

I guess this would be an issue with Graal/native.  But no reason it couldn't work with JVM mode.

[Georgios Andrianakis]

One reason is that we use that information to generate some build time resources, like the OpenAPI schema.

We also seem to use it to register various Vert.x handlers with build time information.

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/CAL%3DE%3DjTrvBBsSz-2kqH%3DbcWnaoSzUrfSGXQ8_uhz%2BtLSOCSQtQ%40mail.gmail.com.

[Jonathan Roques]

Hey, 

I'm the user Bill mentioned :) I got your point and it's a very valid one thank you for the explanation. It's just sad because I'm stuck with the quarkus lambda REST extension and won't be able to get the benefits of the HTTP one. 

[Jason Greene]

I wonder if it makes sense to have an optional dynamic redispatch URL mapping (not a formal redirect, but a secondary dispatch). In this way the main tree is still fixed, but you have this intermediary than can remap into that fixed tree.

To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/CALeTM-%3DSpCs5Dfw_u-cxhLtPkFGjb1gjL8-eKt-gnhw8e9Y%2B8Q%40mail.gmail.com.

[William Burke]

I just find it weird that AWS changes root path based on dev stages.

Jason, the problem with redispatching is that your resources may be generating links.  You'd lose a bit of the link generating facilities of JAX-RS for instance if the root path isn't correct.

[Jonathan Roques]

Exactly, I mean the REST lambda extension works just well with stages, custom domains and so on - where the HTTP doesn't. FYI I also opened a ticket at aws github, asking why don't they provide the raw resource path : https://github.com/aws/aws-lambda-java-libs/issues/240 

[David Lloyd]

Could the application be registered at both (or all?) paths statically?  And maybe capture that path segment to give the app an idea of which one was used, if necessary?

To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/CAL%3DE%3DjRCak2QWDamkwWEMM8PNyLw0Avb7QdzUUsPt82v7YsaQQ%40mail.gmail.com.

--

- DML • he/him

[Jason Greene]

Agree. Does it really require this? The docs speak of this as if it is a customizable template.

For example:

https://docs.aws.amazon.com/apigateway/latest/developerguide/aws-api-gateway-stage-variables-reference.html

[Jonathan Roques]

@jason I'm sorry I don't get what you said by "does it really require this" ? 

[Jonathan Roques]

Do you mean that I should register "/dev/deals" "/prod/deals" and so on ? 

[David Lloyd]

That was my thought. Granted it's been a while since I've messed with JAX-RS, but that seems like it could get around the problem.

To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/24c9247f-dbc6-4cd5-9a9c-da3d7dbd9065n%40googlegroups.com.

--

- DML • he/him