Persist named rollout plans for reuse by clients

It seems to me that we will have multiple clients using the management api to deploy to domain and they all today need to somehow define at every deployment the rollout plan to use if not just the hardwired default.

To avoid having to redefine that everytime it means clients such as IDE's, management console, command line tools will all have to somehow be able to persist this information in their own local setup and these will probably all be a little bit different and thus not shareable.

Thus I suggest that it should be possible to define named rollout plan settings that all the clients can query and provide as named arguments in the managed deployments instead of it being up to every client to define it.