missing 'StrongType' experience in GUI

azMantas commented 3 years ago

it would be great to use 'strongType' functionality for our portal users.
That's what I have in my tempalte parameters file

  "parameters": {
        "resourceTypes": {
            "type": "String",
            "metadata": {
                "strongType": "Microsoft.Network/virtualNetworks/subnets"
            }
        },
        "location": {
            "type": "string",
            "metadata": {
                "strongType": "location"
            }
        },
        "vmSKUs": {
            "type": "string",
            "metadata": {
                "strongType": "vmSKUs"
            }
        },
        "existingResourceGroups": {
            "type": "string",
            "metadata": {
                "strongType": "existingResourceGroups"
            }
        },
        "thatWorks": {
            "type": "String",
            "defaultValue": "123",
            "allowedValues": [
                "abc",
                "def",
                "123"
            ],
            "metadata": {
                "strongType": "thatWorks"
            }
        }
    },

and that's how it looks like in a portal.

alex-frankel commented 3 years ago

We are going to be supporting createUiDefinition to support this scenario going forward. This should give you a lot more capability than what is currently possible with policy's strongType.

azMantas commented 3 years ago

great! can we expect to get this functionality before summer?

alex-frankel commented 3 years ago

Yes it should be done by then - cc @apclouds and @TarunSunkaraneni as FYI

kmgrime commented 2 years ago

@alex-frankel Last update here was 1 year ago - anything new?

alex-frankel commented 2 years ago

The equivalent of strong type is provided by the UiFormDefinition JSON file which you can associate with a Template Spec. We detailed this in #58, so I'm going to close this one.

Azure / template-specs

missing 'StrongType' experience in GUI #47