However, it seems that in doing that change we broke passing the application space constraints along with the bindings as spaces that the machine needs. (It is the set of all bindings + all space constraints that determine the machine provisioning.)
While there is a workaround, I would certainly consider this to be a regression.
As mentioned in https:/ /discourse. juju.is/ t/aws-spaces- in-2-8/ 3417
Juju 2.8 got updated so that bindings on an application get properly passed through to the underlying machine as space constraints.
However, it seems that in doing that change we broke passing the application space constraints along with the bindings as spaces that the machine needs. (It is the set of all bindings + all space constraints that determine the machine provisioning.)
While there is a workaround, I would certainly consider this to be a regression.