rsampaio
commented
2 years ago Hi,
The spec doesn't prevent the broker from implementing this behavior, if your broker receive the VM uuid or name as a provisioning parameter that is required the payload validation should help enforce these parameters are present and from the implementation perspective there is no blockers in the spec that prevents it.
Please re-open if you still have questions and apologies for the delay to reply
What is the problem? Displaying for the user only those service plans that can be used for the parameters specified by the user during provisioning.
Who does this affect? Service broker authors / platform authors?
Additional context
Suppose the user has virtual machines (VM) with different resources (memory, hard disk, cpu)
The user wants to install the message queue broker cluster on specific VMs. He specifies a list of these VMs as a provisioning parameters. The broker then check some conditions for the specified VMs and give the user only the plans that can be used for the specified machines (not all availbale plans)