Sean, You are not considering the parameter/option "cross_az_attach". That feature defines a constraint in the cloud environment. Therefore, it should be considered when executing migrations processes. I see that you want to call a feature, but it is clearly a bug (at least under our understanding). The code is there, valid, and resolves the problem with a simple solution. If you guys would not like it to be accepted, that is fine...¯\_(ツ)_/¯....
Anyways, it seems that this is not going to move further. At least, we have all of this mapped.
Sean, You are not considering the parameter/option "cross_az_attach". That feature defines a constraint in the cloud environment. Therefore, it should be considered when executing migrations processes. I see that you want to call a feature, but it is clearly a bug (at least under our understanding). The code is there, valid, and resolves the problem with a simple solution. If you guys would not like it to be accepted, that is fine... ¯\_(ツ)_ /¯....
Anyways, it seems that this is not going to move further. At least, we have all of this mapped.