[
https://issues.apache.org/jira/browse/ARIA-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166442#comment-16166442
]
Ran Ziv commented on ARIA-381:
------------------------------
See [this|https://cloudifysource.atlassian.net/browse/CFY-7186] and [the
relevant PR|https://github.com/cloudify-cosmo/cloudify-cli/pull/661] for a
solution
> Misleading error message if invalid YAML provided as input file
> ---------------------------------------------------------------
>
> Key: ARIA-381
> URL: https://issues.apache.org/jira/browse/ARIA-381
> Project: AriaTosca
> Issue Type: Bug
> Reporter: Ran Ziv
> Priority: Minor
>
> For {{aria services create}}, if the inputs given are in the form of a YAML
> file, but the YAML is invalid (for example: alignment issues), the user has
> absolutely no way of knowing. The error they'll get is:
> {noformat}
> Invalid input: me.yaml. It must represent a dictionary. Valid values can be
> one of:
> - A path to a YAML file
> - A path to a directory containing YAML files
> - A single quoted wildcard based path (e.g. '*-inputs.yaml')
> - A string formatted as JSON/YAML
> - A string formatted as key1=value1;key2=value2
> {noformat}
> The reason is that we're hiding the internal error that causes parsing to
> fail.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
