Loading...

XML

Word

Printable

Blocked:
False
Blocked Reason:
None
Ready:
False
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
QE Test Coverage:
+
Target Release:

7.4.z.GA
Test Coverage:

+
Git Pull Request:
https://github.com/jbossas/wildfly-core-eap/pull/1225
Steps to Reproduce:
Hide

Configure Git support to manage the configuration history [1]. Execute the following command where the location is invalid:

[standalone@localhost:9990 /] :publish-configuration(location="invalid_location") { "outcome" => "success", "result" => "" }

Expected result: An error to be thrown because location="invalid_location".

[1] https://docs.wildfly.org/28/Admin_Guide.html#Configuration_file_git_history
Show
Configure Git support to manage the configuration history [1] . Execute the following command where the location is invalid: [standalone@localhost:9990 /] :publish-configuration(location= "invalid_location" ) { "outcome" => "success" , "result" => "" } Expected result: An error to be thrown because location="invalid_location". [1] https://docs.wildfly.org/28/Admin_Guide.html#Configuration_file_git_history
Intelligence Requested:
Market:

The publish-configuration command shouldn't complete with "outcome" => "success" when the git location is not valid:

[standalone@localhost:9990 /] :publish-configuration(location="invalid_location")
{
    "outcome" => "success",
    "result" => ""
}

causes

JBEAP-25746 (7.4.z) Align log message IDs in ControllerLogger with upstream

clones

WFCORE-6351 The publish-configuration command doesn't throw an error when the git location is invalid

is incorporated by

JBEAP-24808 [GSS](7.4.z) Upgrade WildFly Core from 15.0.26.Final-redhat-00001 to 15.0.27.Final-redhat-00001