-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quarkus-style configuration of pact location and broker #9
Comments
This should be quite straightforward and perhaps even a no-op (apart from testing), since the broker config can be set by setting the
|
I retract my earlier optimism. The Pact classes read directly from the system properties, which means they wouldn't see anything set in We'd also need to think about precedence if config is set with a system property and in application properties (which Quarkus config may automatically sort out for us), and if it's set in an annotation and in application properties (which Quarkus config would not help with). |
@holly-cummins I used a custom ValueResolver for using the application.properties.file:
or for the .env file:
Usage: |
@kmscheuer Ohh, that's a good idea! I/we could probably insert a Quarkus-aware resolver automatically once https://github.com/orgs/quarkusio/projects/30 is done. |
Refined and combined it a bit, maybe that's helpful:
|
We should make sure things set in application.properties are made available to the tests.
This is related to #3, but different enough that it should get its own issue. The other issue is about enabling dynamic behaviour in the annotation, this is about more general quarkus-friendly config, as we do for many other extensions.
The text was updated successfully, but these errors were encountered: