[✨ Triage] dotnet/aspire#10343 by eerhardt - Support InteractionInput.InputType with both freeform and suggested cho ... #1218
Description
Triage for dotnet/aspire#10343.
Repo filter: area-dashboard issues.
MihuBot version: 4431de.
Ping MihaZupan for any issues.
This is a test triage report generated by AI, aimed at helping the triage team quickly identify past issues/PRs that may be related.
Take any conclusions with a large grain of salt.
dotnet/aspire#10343: Support InteractionInput.InputType with both freeform and suggested choices (useful for Azure Subscriptions) by eerhardt
[Tool] Searching for InteractionInput.InputType freeform suggestions, InteractionInput.InputType arbitrary input, InteractionInput.InputType allow custom value, InteractionInput.InputType suggested choices, Azure Subscription input suggestions, InteractionInput hybrid mode (IncludeOpen=True, IncludeClosed=True, IncludeIssues=True, IncludePullRequests=True, Repository=dotnet/aspire)
[Tool] Found 26 issues, 90 comments, 26 returned results (12077 ms)
Here are the most relevant related issues and discussions for issue #10343, "Support InteractionInput.InputType with both freeform and suggested choices (useful for Azure Subscriptions)":
1. Issue #10344 (July 2025) - "Query the list of available Azure subscriptions during provisioning prompting"
- This issue was opened by the same author, eerhardt, and directly references #10343 as a prerequisite.
- It requests the ability to query and display a list of Azure subscriptions for the user to select during provisioning, but notes that users may also need to enter a subscription manually.
- The author explicitly states: "We may need to wait for Support InteractionInput.InputType with both freeform and suggested choices (useful for Azure Subscriptions) (dotnet/aspire#10343) in order to do this."
- This shows that the hybrid input mode is a recognized requirement for improving the Azure subscription selection experience.
2. PR #10038 (June–July 2025) - "Add Azure provisioning command handling and settings configuration"
- This PR and its discussion are the origin of the feature request in #10343.
- In the comments, eerhardt says:
"I plan on openining an interaction service feature request tomorrow to support an input that allows both a list of options and the ability to enter in a free form value."
- The discussion highlights the current limitation: if you show a list, you can't enter something not in the list, which is problematic for Azure Subscription IDs.
- The PR implements prompting for subscription and location, but the limitation of not being able to enter arbitrary values is called out as a gap.
3. Issue #9807 (June–July 2025) - "Prompt for values"
- This issue and its related PRs (#9943, #10235) discuss the general design of prompting for user input, including the need for select lists and freeform entry.
- davidfowl comments:
"We need to be able to show to select list as well and get back a list of options. Maybe this should be a form builder 😅"
- mitchdenny and others discuss the need for the prompting system to support both selection from a list and arbitrary input, especially for CLI and dashboard parity.
- The issue and its comments show that the need for hybrid input (suggested + freeform) has been recognized as a general requirement, not just for Azure subscriptions.
4. PR #9943 (June 2025) - "Interaction service"
- Implements the core
InteractionServiceand discusses the design of input types. - JamesNK comments:
"IMO have one class and have all properties on it for different input types. Input types will ignore properties that don't apply to them, e.g. checkbox ignores required, text ignores options, etc."
- The discussion is about extensibility and flexibility of input types, which is relevant to supporting hybrid input modes.
5. Issue #1478 (Dec 2023–Feb 2024) - "Introduce prompting behavior to inputs for Aspire manifests"
- This older issue discusses the need for prompting users for input, including the idea of pick lists and validation rules.
- mitchdenny writes:
"The
promptfield could be expanded to support things like creating pick lists and simple validation rules. Some resource types which are intrinsically linked with a particular cloud (e.g. Azure OpenAI) might even have the ability to have a resource picker (with fallback behavior)." - The concept of fallback (i.e., allowing manual entry if the picker doesn't suffice) is similar to the hybrid input mode requested in #10343.
6. PR #10056 (June 2025) - "Rename interaction inputs, improve input dialog UX"
- While not directly about hybrid input, this PR shows ongoing work to generalize and improve the input dialog system, which is relevant to future extensibility for new input types.
7. Issue #10049 (June 2025) - "InteractionService should expose InteractionInput-based APIs for requesting confirmation"
- Discusses the need to generalize input types and unify the way different kinds of prompts are handled, which is related to the extensibility needed for hybrid input types.
Summary
- The need for a hybrid input mode (suggested choices + freeform entry) is well-recognized, especially for Azure Subscription selection.
- The limitation is called out in PR #10038, and #10344 is blocked on this feature.
- The general prompting infrastructure (see #9807, #9943) is being designed with extensibility in mind, but currently does not support this hybrid mode.
- There is precedent and support for this feature in both recent and older discussions, and it is seen as important for both usability and flexibility.
No existing issue or PR implements this hybrid input mode yet, but it is a known gap and a logical next step for the interaction service.
Directly Related Issues/PRs:
- #10344 - Query the list of available Azure subscriptions during provisioning prompting
- #10038 - Add Azure provisioning command handling and settings configuration
- #9807 - Prompt for values
- #9943 - Interaction service
- #1478 - Introduce prompting behavior to inputs for Aspire manifests
If you need more detail on any of these discussions, let me know!