Uploaded image for project: 'CLOUDIFY (R&D)'
  1. CY-708

Deployment inputs from YAML file not properly recognized

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Unprioritized
    • Resolution: Done
    • Fix versions: None
    • Labels:
    • Steps to Reproduce:
      Hide
      Environment:
      OS (CLI), HA cluster, cloud provider
      ------------------------------------


      Steps to reproduce:
      ------------------
      1.
      2.
      3.


      Expected result:
      ---------------


      Actual result:
      -------------
      Show
      Environment: OS (CLI), HA cluster, cloud provider ------------------------------------ Steps to reproduce: ------------------ 1. 2. 3. Expected result: --------------- Actual result: -------------
    • Severity:
      Medium
    • Target Version:
    • Premium Only:
      no
    • Found In Version:
      4.4
    • Sprint:
      4.5.5 Sprint 1
    • Bug Type:
      regression bug
    • Customer Encountered:
      Yes
    • Release Notes:
      yes

      Description

      Types of the deployment inputs from YAML file are not preserved in case there are strings containing values which can be casted to another types, eg.: "12" can be casted to number 12, "[1,2,3]" can be casted to array [1,2,3].

      As for now we try to cast input values to the number, boolean, array, object types.
      But in some cases user may want to send something explicitly as a string. We should allow explicit string type setting by surrounding the input value with double quotes: "<content>" in deployment creation modals.

        Attachments

          Activity

            People

            • Assignee:
              jakub.niezgoda Jakub Niezgoda
              Reporter:
              jakub.niezgoda Jakub Niezgoda
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: