]
James Perkins moved JBEAP-8868 to WFCORE-2300:
----------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-2300 (was: JBEAP-8868)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Domain Management
(was: Domain Management)
(was: User Experience)
Affects Version/s: (was: 7.1.0.DR7)
ReadResourceNameOperationStepHandler does not check if the resource
exists before returning the resource name
-------------------------------------------------------------------------------------------------------------
Key: WFCORE-2300
URL:
https://issues.jboss.org/browse/WFCORE-2300
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Reporter: James Perkins
Assignee: James Perkins
Priority: Minor
Trying to read the {{category}} attribute on a nonexistent logger results in success:
{code}
[standalone@localhost:9990 /]
/subsystem=logging/logger=aaaaaa:read-attribute(name=category)
{
"outcome" => "success",
"result" => "aaaaaa"
}
{code}
Any other attributes can't be read and the operation correctly fails, e.g.:
{code}
[standalone@localhost:9990 /]
/subsystem=logging/logger=aaaaaab:read-attribute(name=level
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0216: Management resource '[
(\"subsystem\" => \"logging\"),
(\"logger\" => \"aaaaaab\")
]' not found",
"rolled-back" => true
}
{code}
This behavior is confusing, the operation should fail for any attribute on a nonexistent
logger.