Skip to main content

Dynamic Blueprint Inputs

Feature RequestsBlueprints

Create dynamic input option. I know maps are available to partially solve this problem but the documentation specifically calls out that maps cannot be used in the input section and vice versa.

For example, if I am provisioning an Azure function app, I can set the runtime in the blueprint. I can create an option field that allows the user to pick "Python - 3.12", "Python - 3.11", "Node - 22", "Node - 20", etc... I also have an option to choose "Docker", however,  I also then want to allow the user to pass a particular image name and tag that cannot be anticipated and included as a dropdown option. Is there a way to make a text field visible to accept user input only if the user has select "Docker" as the run time? Or even more simply, if I choose Python as the runtime, dynamically set the version drop down to 3.12, 3.11, 3.10 vs if I choose Node as the runtime, the version drop down sets to 22, 20, 18.

Workaround
Status: 🔭 Discovery1 comment

This request was merged into another request

Comments1

  • Black Breeze

    •

    May 29, 2025

    Thanks for the request! A few questions to help us understand better: **What's driving this need?** - Are you trying to reduce the number of blueprints you maintain? - Is this about making it easier for non-technical users? - Something else? **How are you solving this today?** - Do you have separate blueprints for each runtime? - Are users confused by too many options? **What would success look like?** - Fewer support requests from users? - Faster time to provision? - Less blueprint maintenance? **One thing to consider:** Instead of dynamic inputs, would a blueprint 'wizard' that helps users find the right pre-built blueprint solve the same problem? That way all logic stays in code (reviewable, testable) but users still get a guided experience.