Is your feature request related to a problem? Please describe.
I love the Component Builder, but it will be great to have a Component Viewer (in contrast with the see Raw YAML Component).
It would be also great to have an apply button that prompts for authorization to apply the YAML via the agent.
This would highly speed up the developer tasks of manipulating their component configurations.
For more complex setups, if GitOps is being used, the YAML approach is ok.
Describe the solution you'd like.
The forms seems to be generated by Schemas, which makes me think that we can have a Form to display the parameters of a given component, allowing people to for example change the scope of a component.
What is a component viewer? What would you want to see?
Today Conductor manages (install, upgrade, configure) Dapr control plane, but it doesn't modify in any way the app workloads. We might consider this for development clusters once we have more asks to do so. In the time downloading the file + kubectl apply is the way.
Correct, it is based on component schemas. Can you give me examples what parameters and what values can be offered (that don't exist today)?
Is your feature request related to a problem? Please describe.
I love the Component Builder, but it will be great to have a Component Viewer (in contrast with the see Raw YAML Component). It would be also great to have an apply button that prompts for authorization to apply the YAML via the agent. This would highly speed up the developer tasks of manipulating their component configurations.
For more complex setups, if GitOps is being used, the YAML approach is ok.
Describe the solution you'd like.
The forms seems to be generated by Schemas, which makes me think that we can have a Form to display the parameters of a given component, allowing people to for example change the scope of a component.
Additional context.