-
Notifications
You must be signed in to change notification settings - Fork 80
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
WIP #381
WIP #381
Conversation
core/yaml.adoc
Outdated
The aim of this proposal is to be able to inject external configuration in a YAML format to WildFly in order to customize an existing configuration. | ||
It is out of the scope of this proposal to provide support to define a complete server configuration in YAML: as such you won't be able to add a new extension using a YAML file. | ||
We also want this to be *idempotent*: that means that starting and restarting the server with the same command line should produce the same result and shouldn't fail. | ||
This feature is expected to be used as base for Bootable JAR implementation, it is not expected to be called directly by user (TODO get confirmation on this from Jeff and Brian and on how to 'hide' the feature). |
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 feature should not be hidden. It will be leveraged by the Bootable Jar Maven plugin
|
||
=== Issue | ||
|
||
* https://issues.redhat.com/browse/WFCORE[WFCORE-XXXX] |
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.
Missing upstream issue
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.
none currently
External files will take precedence over the XML configuration ones. Then order will follow the command line. | ||
|
||
* If the resource is already defined then all we have to du is updating its attrbiutes using the `write-attribute` operation. | ||
* If the YAML part define an empty resource and the resource already exists: log a WARNING, otherwise try to add it. |
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.
why do you log a WARN and do not fail?
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.
Because it doesn't do anything, failing seems a bit 'harsh' and would add the resource if it was missing from the XML.
Superseded by ttps://github.com//pull/384 |
No description provided.