[
https://issues.jboss.org/browse/AS7-713?page=com.atlassian.jira.plugin.sy...
]
Brian Stansberry commented on AS7-713:
--------------------------------------
The API description:
[domain@localhost:9999 /] cd management-client-content=rollout-plans
[domain@localhost:9999 management-client-content=rollout-plans]
:read-resource-description(recursive=true,inherited=false,operations=true)
{
"outcome" => "success",
"result" => {
"description" => "Storage information about a set of named
management update rollout plans useful to management clients that are stored in the domain
content repository. The child resources under this resource provide access to these plans
to management clients, allowing clients to use the plans by referencing them by name,
avoiding the need to recreate them for each use.",
"attributes" => {"hash" => {
"type" => BYTES,
"description" => "The hash of all stored rollout plans. Used
internally by host controllers to locate rollout plan content.",
"expressions-allowed" => false,
"nillable" => true,
"min" => 20L,
"max" => 20L,
"access-type" => "read-only",
"storage" => "configuration"
}},
"operations" => {"add" => {
"operation-name" => "add",
"description" => "Adds the capability to store named rollout
plans.",
"request-properties" => {"hash" => {
"type" => BYTES,
"description" => "The hash of all stored rollout plans.
Used internally by host controllers to locate rollout plan content.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"min" => 20L,
"max" => 20L
}},
"reply-properties" => {}
}},
"children" => {"rollout-plan" => {
"description" => "A stored rollout plan.",
"model-description" => {"*" => {
"description" => "A stored rollout plan.",
"attributes" => {
"content" => {
"type" => OBJECT,
"description" => "The rollout plan content, in
JBoss DMR form.",
"expressions-allowed" => false,
"nillable" => false,
"access-type" => "read-write",
"storage" => "runtime",
"restart-required" => "no-services"
},
"hash" => {
"type" => BYTES,
"description" => "The hash of the rollout plan
content.",
"expressions-allowed" => false,
"nillable" => false,
"min" => 20L,
"max" => 20L,
"access-type" => "read-only",
"storage" => "runtime"
}
},
"operations" => {
"store" => {
"operation-name" => "store",
"description" => "Updates the content of an
existing persisted rollout plan, after first checking that the provided 'hash'
parameter matches the current rollout plan hash. Fails if the hashes do not match. Using
this operation instead of the 'write-attribute' operation for the
'content' attribute provides a guarantee that the update will not conflict with a
previous update unknown to the caller.",
"request-properties" => {
"hash" => {
"type" => BYTES,
"description" => "The value the caller
believes to be the hash of the rollout plan content that is being replaced.",
"expressions-allowed" => false,
"required" => true,
"nillable" => false,
"min" => 20L,
"max" => 20L
},
"content" => {
"type" => OBJECT,
"description" => "The updated rollout
plan content, in JBoss DMR form.",
"expressions-allowed" => false,
"required" => true,
"nillable" => false
}
},
"reply-properties" => {}
},
"remove" => {
"operation-name" => "remove",
"description" => "Removes a rollout plan from
the persistent store.",
"request-properties" => {},
"reply-properties" => {}
},
"add" => {
"operation-name" => "add",
"description" => "Adds a rollout plan to the
persistent store.",
"request-properties" => {"content" => {
"type" => OBJECT,
"description" => "The rollout plan content,
in JBoss DMR form.",
"expressions-allowed" => false,
"required" => true,
"nillable" => false
}},
"reply-properties" => {}
}
},
"children" => {}
}}
}}
}
}
Persist named rollout plans for reuse by clients
------------------------------------------------
Key: AS7-713
URL:
https://issues.jboss.org/browse/AS7-713
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Max Rydahl Andersen
Assignee: Brian Stansberry
Fix For: 7.1.0.CR1
It seems to me that we will have multiple clients using the management api to deploy to
domain and they all today need to somehow define at every deployment the rollout plan to
use if not just the hardwired default.
To avoid having to redefine that everytime it means clients such as IDE's, management
console, command line tools will all have to somehow be able to persist this information
in their own local setup and these will probably all be a little bit different and thus
not shareable.
Thus I suggest that it should be possible to define named rollout plan settings that all
the clients can query and provide as named arguments in the managed deployments instead of
it being up to every client to define it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira