[
https://issues.apache.org/jira/browse/CLOUDSTACK-9457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15685878#comment-15685878
]
ASF GitHub Bot commented on CLOUDSTACK-9457:
--------------------------------------------
Github user koushik-das commented on the issue:
https://github.com/apache/cloudstack/pull/1767
@serg38 @nvazquez Thanks for the update. As I understand form some of the
detail parameter examples, these are tied to the lifecycle of the entity
(create/destroy or start/stop of the VM). If thats the case then it make sense
to pass on these details along with the corresponding lifecycle APIs rather
than creating new APIs. Do you see any use case where the details are not tied
to entity lifecycle?
> Allow retrieval and modification of VM and template details via API and UI
> --------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9457
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9457
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
> Affects Versions: 4.10.0.0
> Reporter: Nicolas Vazquez
> Assignee: Nicolas Vazquez
> Priority: Minor
>
> h2. Introduction
> As suggested on [9379|https://issues.apache.org/jira/browse/CLOUDSTACK-9379],
> it would be nice to be able to customize vm details through API
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
