[
https://issues.jboss.org/browse/WFCORE-380?page=com.atlassian.jira.plugin...
]
Brian Stansberry reassigned WFCORE-380:
---------------------------------------
Assignee: luck3y
Ken,
This may or may not conflict with the task of supporting exploded deployments in the
content repository. Possible conflicts:
1) Adding an attribute for this just doesn't fit nicely with whatever API we add for
managing exploding deployments.
2) Users may think this attribute will allow them to suck down a zipped version of an
exploded deployment. (I guess this is a variant of 1) above.)
It's ok to reschedule this out of 1.0.0.CR1 if you're concerned about adding this
API now before the full picture is clear.
Operations to read content from the content repository
------------------------------------------------------
Key: WFCORE-380
URL:
https://issues.jboss.org/browse/WFCORE-380
Project: WildFly Core
Issue Type: Feature Request
Components: Domain Management
Reporter: Brian Stansberry
Assignee: luck3y
Priority: Minor
Fix For: 1.0.0.CR1
Ability to pull data out of the content repository. We can do that with rollout plans,
but not for deployments or if we add deployment content overlays.
Basically, if the user loses the original of the deployment, let's let them get it
back via the management API and remove the temptation for them to hack into the
repository.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)