cdf-tk deploy fails on fresh space due to unresolved requires constraints

Hi

We've hit a bug in cdf-tk (reproduced on 0.8.147 and 0.8.155) when deploying containers to a brand new space.

We have 98 containers in a new space. One container has no constraints, but others reference it via a requires constraint pointing to the same space. cdf-tk sends all containers in a single batch. The CDF API seems to validates requires constraints against what already exists in CDF not against other items in the same batch so it rejects the entire batch with this error:

Cannot create requires constraint 'requireMetadata' in container
'sp_xxx:ContainerB'.
Target container 'sp_xxx:ContainerA' does not exist.

cdf-tk should sort containers by their requires dependencies before batching, so dependency free containers like containerA are sent before the containers that depend on them.

We'd appreciate a fix in an upcoming release, or any insights regarding this issue.

Thanks