Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0B130200C4C for ; Tue, 4 Apr 2017 13:25:47 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 099AA160B90; Tue, 4 Apr 2017 11:25:47 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 4D506160B81 for ; Tue, 4 Apr 2017 13:25:46 +0200 (CEST) Received: (qmail 20980 invoked by uid 500); 4 Apr 2017 11:25:45 -0000 Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@brooklyn.apache.org Delivered-To: mailing list dev@brooklyn.apache.org Received: (qmail 20962 invoked by uid 99); 4 Apr 2017 11:25:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Apr 2017 11:25:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id C569AC036E for ; Tue, 4 Apr 2017 11:25:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id yY-IdcPJpCez for ; Tue, 4 Apr 2017 11:25:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 8D6635FCD9 for ; Tue, 4 Apr 2017 11:25:42 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id E7EDAE09D6 for ; Tue, 4 Apr 2017 11:25:41 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 95B932401A for ; Tue, 4 Apr 2017 11:25:41 +0000 (UTC) Date: Tue, 4 Apr 2017 11:25:41 +0000 (UTC) From: "Sam Corbett (JIRA)" To: dev@brooklyn.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (BROOKLYN-463) Improve CLI login feedback MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 04 Apr 2017 11:25:47 -0000 Sam Corbett created BROOKLYN-463: ------------------------------------ Summary: Improve CLI login feedback Key: BROOKLYN-463 URL: https://issues.apache.org/jira/browse/BROOKLYN-463 Project: Brooklyn Issue Type: Sub-task Reporter: Sam Corbett I expected a {{br login}} command to prompt for a username and password when only run with the URL for the server. Instead it exits with no useful information: {code} $ br login http://localhost:8081 $ echo $? 2 {code} Giving a username behaves well: {code} $ br login http://localhost:8081 sam Enter Password: {code} The CLI should either prompt for a username or print a usage summary when only invoked with a URL. If prompting for the username it could also allow simply {{br login}} and prompt for the endpoint parameter. -- This message was sent by Atlassian JIRA (v6.3.15#6346)