ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nate Cole (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-18683) Argument for manually setting CURRENT is unclear
Date Mon, 04 Dec 2017 20:16:00 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-18683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nate Cole resolved AMBARI-18683.
--------------------------------
    Resolution: Won't Do

> Argument for manually setting CURRENT is unclear
> ------------------------------------------------
>
>                 Key: AMBARI-18683
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18683
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>             Fix For: 3.0.0
>
>
> It is currently possible to set the CURRENT {{repo_version}} for a component.  The API
is a little misleading.  The call below should also check for the version string, not just
the display name. Could also check for the id itself too.
> {noformat}
> PUT /api/v1/clusters/c1/stack_versions
> {
>   "ClusterStackVersions": {
>     "force": true,
>     "state": "CURRENT",
>     "repository_version": "HDP-2.5.1.0"    <------- must be display name
>   }
> }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message