We would like to be able to consume environments from a shared pool containing a mixture of iaas types. This way we could supplement our v-sphere environments with aws environments when demand is high.

Unfortunately our vsphere environments are not visible from our untagged aws workers. This means that we must decide what iaas our environment is hosted on, then define our pool-resource and worker tags to match.

It would be preferable to be able to claim an environment, determine it's iaas, and then decide what worker tags the task needs, all in the course of a single job build.