can you do conditional attributes for module type profiles?

[rconkor]

Example JSON:

{
    "properties": {
        "hot_swappable": {
          "default": false,
          "title": "Hot-swappable",
          "type": "boolean"
        },
        "size": {
            "description": "Raw disk capacity",
            "title": "Size (GB)",
            "type": "integer"
        },
        "speed": {
            "title": "Speed (RPM)",
            "type": "integer"
        },
        "type": {
            "default": "SSD",
            "enum": [
                "HD",
                "SSD",
                "NVME"
            ],
            "title": "Disk type",
            "type": "string"
        },
        "generation": {
            "enum": [
                "Gen3",
                "Gen4",
                "Gen5"
            ],
            "title": "NVMe Generation",
            "type": "string"
        },
    },
    "required": [
        "size"
    ]
}

Is there a way to make the 'generation' field only show up if the 'type' option is 'nvme' ?

[jeremystretch]

Good question! NetBox validates profile attributes using a JSON schema, which does support conditionals. This should work for your example:

{
    "properties": {
        "hot_swappable": {
          "default": false,
          "title": "Hot-swappable",
          "type": "boolean"
        },
        "size": {
            "description": "Raw disk capacity",
            "title": "Size (GB)",
            "type": "integer"
        },
        "speed": {
            "title": "Speed (RPM)",
            "type": "integer"
        },
        "type": {
            "default": "SSD",
            "enum": [
                "HD",
                "SSD",
                "NVME"
            ],
            "title": "Disk type",
            "type": "string"
        },
        "generation": {
            "enum": [
                "Gen3",
                "Gen4",
                "Gen5"
            ],
            "title": "NVMe Generation",
            "type": "string"
        }
    },
    "required": [
        "size"
    ],
    "if": {
        "properties": {
            "type": {
                "const": "NVME"
            }
        }
    },
    "then": {
        "required": ["generation"]
    }
}

[rconkor]

I see what you're doing, requiring conditional validation. That will work.
Is there a way to control the order of the fields? In your example, NVMe Generation is at the top, while 'Drive Type' is at the bottom. Any way to have the Generation be below 'Drive Type' ?

I'm getting a validation error if I attempt using the uiSchema, so wondering if you have another method?

EDIT: so the UI appears to be based on property name sorted alphabetically. As a workaround I renamed the "generation" property to "u_generation" so it coms after "type". A little clunky though.