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
WFLY-12759 Extract microprofile-config galleon layer from observability #12776
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will need an entry in the testsuite/layers/pom.xml. All layers should have an entry there as that is the basic boot validation for the layer.
It also needs an update to https://github.com/wildfly/wildfly/blob/master/docs/src/main/asciidoc/_admin-guide/Galleon_provisioning.adoc
f242b47
to
4119ade
Compare
@bstansberry Fixed. |
@jmesnil OK with you? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this. Looks good.
Actually, would it make any sense to document this in |
@rhusar MicroProfile Config is usable directly by applications, so any layer at all could possibly be decorated with this one. It seems simpler to document them all too. |
https://issues.jboss.org/browse/WFLY-12759
Microprofile specs like OpenAPI don't require metrics nor health, suggesting the microprofile layers should be more granular.