[
https://issues.apache.org/jira/browse/WHIRR-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457931#comment-13457931
]
Steve Loughran commented on WHIRR-658:
--------------------------------------
the basic operations {{stop-services}} {{start-services}} and
{{restart-services}} all have the same behaviour, though {{destroy-cluster}}
isn't and instead just warns -so stays nicely idempotent.
A clean design here would be to have a specific exception
{{UnknownClusterException extends IOException}} that gets thrown on a match
failure -which is then handled differently by the specific entry points.
> list-cluster could report "unknown cluster" when handed an unknown cluster
> name
> -------------------------------------------------------------------------------
>
> Key: WHIRR-658
> URL: https://issues.apache.org/jira/browse/WHIRR-658
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.9.0
> Reporter: Steve Loughran
> Priority: Minor
>
> when you give {{whirr list-cluster}} an unknown cluster name, you get a file
> not found exception and a stack trace. This could be replaced with a "cluster
> not known" message
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
