We're updating the issue view to help you get more done. 

Align CLI and GUI behavior regarding parsing blueprint input files, when providing empty strings

Description

Blueprint input value for an empty string in a file needs to contain different quoting depending on whether it's going to be loaded via the CLI or GUI.

For a file used via the GUI:
1. The file must contain:
'""' (that's single quote, double quote, double quote, single quote)
2. This results in "" populating in the GUI input as required for an empty string.
3. Success, the blueprint input is empty as desired.

But, for the same file via the CLI:
1. Loaded blueprint input value is shown as:
\"\ (that's backslash, double quote, backslash)
2. Failure - this is neither empty or a valid value for the input in question.
3. Note that the value looks OK in the output of 'cfy deployment inputs'.

Steps to Reproduce

Environment:
OS (CLI), HA cluster, cloud provider
------------------------------------

Steps to reproduce:
------------------
1. Start Deployment Create (Deploy button in Blueprints widget in Local Blueprints page or Create deployment button in Deployments page) or Deployment Update (Update Deployment button on deployment drill down page)
2. Provide YAML file with inptuts with empty value, with boolean value (True/False), with object or array values
3. See that they are not parsed properly

Expected result:
---------------
All types of inputs parsed properly. Especially empty strings parsed properly and send to manager as typed value.

Actual result:
-------------
All types of inputs treatead as strings. Cannot set empty string on inputs with default values defined.

Why Propose Close?

None

Status

Assignee

Jakub Niezgoda

Reporter

Jonathan Abramsohn

Severity

Medium

Target Version

4.4

Premium Only

no

Found In Version

4.3

QA Owner

Lital Hamami

Bug Type

unknown

Customer Encountered

Yes

Customer Name

c238

Release Notes

yes

Priority

None

Sprint

None

Priority

Unprioritized