My question is simple – Why can I set vmw-task=true via the REST api when doing a “clone” but not when deploying from template? (this applies to both content library and a regular template).
The features of the content library are great, but it confounds me that I have to hold open a REST connection for the entire duration of a 'deploy' REST call, especially if the task is “waiting for resources” for a long time.
