[
https://issues.apache.org/jira/browse/CLOUDSTACK-9457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683249#comment-15683249
]
ASF GitHub Bot commented on CLOUDSTACK-9457:
--------------------------------------------
Github user koushik-das commented on the issue:
https://github.com/apache/cloudstack/pull/1767
@nvazquez Can you add use case details that will be addressed by these new
methods? Also what kind of validation will be performed on the inputs and the
state of the entity (VM or template)? Will it be metadata for book keeping only
or will impact the entity during runtime? I am assuming that data will be
stored in the corresponding *details table in DB. How will these APIs impact
already existing data that are created using some other APIs and stored in the
details table?
> 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)
