You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Srimanth Gunturi (JIRA)" <ji...@apache.org> on 2013/10/01 21:55:24 UTC

[jira] [Commented] (AMBARI-3404) Add userId password options to configs script

    [ https://issues.apache.org/jira/browse/AMBARI-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783268#comment-13783268 ] 

Srimanth Gunturi commented on AMBARI-3404:
------------------------------------------

Additional requirements:

* We need to parameterize the Ambari server port and make it an optional param along with username/password.
* We should improve error handling.
** We got an error message "Tag unknown for site global" while setting configs for a customer.  The reason was that the password was set to a custom one (not "admin"), so the API authentication failed.
* For the usage/param description, we should use "CONFIG_TYPE" rather than "SITE_NAME" because we use the attribute name "type" for the Config API.  Also, there are config types that are non "sites" like "global", "mapred-queue-acls", etc.

> Add userId password options to configs script
> ---------------------------------------------
>
>                 Key: AMBARI-3404
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3404
>             Project: Ambari
>          Issue Type: Task
>          Components: client
>    Affects Versions: 1.4.0
>            Reporter: Srimanth Gunturi
>            Assignee: Srimanth Gunturi
>             Fix For: 1.4.1
>
>         Attachments: AMBARI-3404.patch
>
>
> configs.sh is expected to be used during HDP upgrade. We need some improvements:
> * Parameterize username and password
> * Use time lapsed in seconds as tag (currently it uses date e.g. version20131001071839)



--
This message was sent by Atlassian JIRA
(v6.1#6144)