Skip to content

SPIKE: Spike parameter prompting from CLI #9349

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mitchdenny
Copy link
Member

Fixes: #8915

This is a spike on parameter prompting. Plenty of more work to do here but this is just something basic which works.

What I'll probably look to do is have parameter resources fire an event which the backchannel hooks if it is available and drives prompting AFTER the back channel is connected and has asked for parameters.

This will help control flow.

@davidfowl
Copy link
Member

cc @captainsafia

Copy link
Member

@captainsafia captainsafia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good start! Some random thoughts:

  • I assume we'll want some sort of handling for a --no-prompt flag that we can use to disable prompting in CI environments.
  • How do we think about how a validation experience might plug into this? Will it need to be part of the GetParameterValueCallback? Do we build our own validation experience on top of System.ComponentModel or something?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add prompting for parameters in aspire run, aspire publish and aspire deploy.
3 participants