[
https://issues.apache.org/jira/browse/CLOUDSTACK-9457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683805#comment-15683805
]
ASF GitHub Bot commented on CLOUDSTACK-9457:
--------------------------------------------
Github user nvazquez commented on the issue:
https://github.com/apache/cloudstack/pull/1767
Hi @koushik-das @ustcweizhou,
For this new methods as they require the entity id (VM or template) I added
a basic validation to check if the entity is found on DB, but I realize that I
should also validate that entity is not destroyed. This data is to be stored in
*details tables.
About existing API methods, I have checked `updateTemplate` and
`updateVirtualMachines` methods before adding this new methods, and they
provide a way to add/update details (although updateTemplate overrides existing
details). Also, details can be listed on `listTemplates` and
`listVirtualMachines` but thought the best approach was introducing this new
methods to reduce overhead and treat entity details separately instead of
updating/listing the entity every time. What do you think of this approach?
> 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)
