Conditional loading of fields in template UI for Radio button

Hi, I need to load the below react json schema component (conditional field) in template UI:

{
  "title": "Schema dependencies",
  "description": "These samples are best viewed without live validation.",
  "type": "object",
  "properties": {    
    "conditional": {
      "title": "Conditional",
      "$ref": "#/definitions/person"
    }
  },
  "definitions": {
    "person": {
      "title": "Person",
      "type": "object",
      "properties": {
        "Do you have any pets?": {
          "type": "string",
          "enum": [
            "No",
            "Yes: One",
            "Yes: More than one"
          ],
          "default": "No"
        }
      },
      "required": [
        "Do you have any pets?"
      ],
      "dependencies": {
        "Do you have any pets?": {
          "oneOf": [
            {
              "properties": {
                "Do you have any pets?": {
                  "enum": [
                    "No"
                  ]
                }
              }
            },
            {
              "properties": {
                "Do you have any pets?": {
                  "enum": [
                    "Yes: One"
                  ]
                },
                "How old is your pet?": {
                  "type": "number"
                }
              },
              "required": [
                "How old is your pet?"
              ]
            },
            {
              "properties": {
                "Do you have any pets?": {
                  "enum": [
                    "Yes: More than one"
                  ]
                },
                "Do you want to get rid of any?": {
                  "type": "boolean"
                }
              },
              "required": [
                "Do you want to get rid of any?"
              ]
            }
          ]
        }
      }
    }
  }
}

Any suggestions on how to convert this to template.yaml file?

[sharadpattanshetti]

Thanks @defaultbr. I got this one working for the dropdown (select) on the UI. I was looking for Radio button option hence tried adding ui:widget: radio to the yaml. In React Json Schema form it renders as radio button with dependencies however when converted to YAML it does not work. Radio button along with $ref dependencies does not render when added in YAML format

[defaultbr]

@sharadpattanshetti you could test this example

  parameters:
    - title: Creating a API
      required: []
      properties:
        technology:
          type: string
          enum:
            - java
            # - dotnet
            - javascript
            - python

      # Creating a dependency based on the selected technology above
      dependencies:
        technology:
          oneOf:
            - properties:
                technology:
                  enum:
                    - java
                java version:
                  type: "string"
                  enum:
                    - java8
                    - java11

              # Creating a dependency based on the selected java version (not necessary, just for example)
              dependencies:
                java version:
                  oneOf:
                    - properties: 
                        java version:
                          enum:
                            - java8
                        any other option:
                          type: "string"
                          enum:
                            - option1
                            - java build x.y.z
              required: 
                - java version

What I have learned testing the above yml code:

1. Segregate the template in more software catalog, don’t try to merge multiple languages and things to consider in one file, this will make your template a big, very very big and confuse spaghetti.

2. dependency are coupled in the field title/name, so try to use simple names

3. You can’t import (use the $include) external files, so you will return to item 1 above if you plan to consolidate a lot of questions and if’s inside a single template file

Maybe a good use will be to create a catalog entry for Libraries, another for API’s, etc…

If you create a Api and can have deploy in multiple targets, like in kubernetes, azure, aws, gcp, I guess it’s better to have different catalog entry for each one, since you can ask a lot of different things for each option and your template will be hard to read.

Examples:

• Create Api - ON PREM K8S
• Create Api - AWS
• Create Api - GCP
• Create Api - Serverless - Lambda (AWS)
• Create Api - Serverless - Azure Functions (AWS)

(of course, if each one has different requirements and fields)

Maybe I’m totally wrong, since I learned this almost 30 minutes ago, if i find a way to consolidate and avoid a huge spaguetti, I will post here again