Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Sun, 31 Aug 2014 18:10:20 +0000 (UTC)
From: "Shalom Bhooshi (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12738147.1409508603000.471.1409508620630@Atlassian.JIRA>
In-Reply-To: <JIRA.12738147.1409508603000@Atlassian.JIRA>
References: <JIRA.12738147.1409508603000@Atlassian.JIRA>
 <JIRA.12738147.1409508603166@arcas>
Subject: [jira] [Created] (CLOUDSTACK-7458) CloudMonkey does not return a
 failure exit code on empty API response
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Shalom Bhooshi created CLOUDSTACK-7458:
------------------------------------------

             Summary: CloudMonkey does not return a failure exit code on empty API response
                 Key: CLOUDSTACK-7458
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7458
             Project: CloudStack
          Issue Type: Improvement
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Cloudmonkey
         Environment: CloudMonkey 5.2
            Reporter: Shalom Bhooshi


It would be useful to have cloudmonkey return a failure (non-zero) exist code when an empty response is returned from the management server.

e.g. In the following case - the caller script (bash) is required to additionally test whether the output is empty-or-not whereas this would not be needed if cloudmonkey returned an appropriate exit code.

set -e
if sos=$( cloudmonkey list serviceofferings keyword="some_non_existant_so_name" ); then
  if [[ -z $sos ]]; then warn "Empty input"; exit 2; fi
fi


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)