[jboss-jira] [JBoss JIRA] (WFCORE-999) Deprecate the "upload-deployment-*" ops and *perhaps* add upload-content-*" equivalents
[
https://issues.jboss.org/browse/WFCORE-999?page=com.atlassian.jira.plugin...
]
Brian Stansberry updated WFCORE-999:
------------------------------------
Description:
The upload-deployment-* ops are poorly named, as they support uploading any sort of
content, not just deployments. And they also foster the illusion that simply invoking
those ops in some way creates a deployment.
The existing ops should be deprecated.
Beyond that we should *consider* adding equivalent ops named upload-content-*. The same
handler classes can be used; this is just a matter of the OperationDefinition that
produces the metatdata. The text description of the new ops should be tweaked a bit as
well, to remove any use of the term 'deployment'.
*However* it is not certain that we should add these new ops. We should only do it if we
have real uses cases that require a separate upload op followed by a persistent config
change op. In general config change ops that use bits in the content repo should support
directly uploading that content as part of the op, via an attachment stream.
The current use cases for the content repo are deployments, deployment-overlays and
management-client-content. Patches could in theory use it but at the moment do not.
was:
The upload-deployment-* ops are poorly named, as they support uploading any sort of
content, not just deployments. And they also foster the illusion that simply invoking
those ops in some way creates a deployment.
The existing ops should be deprecated.
Beyond that we should *consider* adding equivalent ops named upload-content-*. The same
handler classes can be used; this is just a matter of the OperationDefinition that
produces the metatdata. The text description of the new ops should be tweaked a bit as
well, to remove any use of the term 'deployment'.
*However* it is not certain that we should add these new ops. We should only do it if we
have real uses cases that require a separate upload op followed by a persistent config
change op. In general config change ops that use bits in the content repo should support
directly uploading that content as part of the op, via an attachment stream.
Deprecate the "upload-deployment-*" ops and *perhaps* add
upload-content-*" equivalents
---------------------------------------------------------------------------------------
Key: WFCORE-999
URL: https://issues.jboss.org/browse/WFCORE-999
Project: WildFly Core
Issue Type: Enhancement
Components: Domain Management
Reporter: Brian Stansberry
Priority: Minor
The upload-deployment-* ops are poorly named, as they support uploading any sort of
content, not just deployments. And they also foster the illusion that simply invoking
those ops in some way creates a deployment.
The existing ops should be deprecated.
Beyond that we should *consider* adding equivalent ops named upload-content-*. The same
handler classes can be used; this is just a matter of the OperationDefinition that
produces the metatdata. The text description of the new ops should be tweaked a bit as
well, to remove any use of the term 'deployment'.
*However* it is not certain that we should add these new ops. We should only do it if we
have real uses cases that require a separate upload op followed by a persistent config
change op. In general config change ops that use bits in the content repo should support
directly uploading that content as part of the op, via an attachment stream.
The current use cases for the content repo are deployments, deployment-overlays and
management-client-content. Patches could in theory use it but at the moment do not.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)