Deprecate "reload", "suspend" and "resume" ops on the server-config resource ---------------------------------------------------------------------------- Key: WFCORE-1917 URL: https://issues.jboss.org/browse/WFCORE-1917 Project: WildFly Core Issue Type: Task Components: Management Reporter: Brian Stansberry Assignee: Yeray Borges Labels: domain-mode The /host=x/server-config=y resource is a configuration chunk meant to describe how the HC should set up a server, not an actual runtime resource that represents the server. The runtime resource is /host=x/server=y. But in the early days of AS7 we hadn't worked out how to have a resource for /host=x/server=y when y wasn't actually started, so as a workaround we stuck 'runtime' ops like start/stop/restart on server-config. But that was never conceptually right; it was just a workaround. But then we mistakenly expanded on that by sticking ops like 'reload', 'resume' and 'suspend' on the server-config resource as well. We should deprecate these so we can get rid of them in a future release (EAP 8). Right now they don't work very well; e.g. you can reload, suspend or resume a 'server-config' that isn't even started and the op will succeed. But that's not something this JIRA is meant to address; I'm just pointing it out as evidence of why having these ops on this resource type is conceptually a mess.