Netbox parent prefix vs container

[bigfoot6uk]

Background:

I've been designing a large playbook to take care of our AWS account automation process. As part of the development we've reviewed using terraform netbox modules as well.
The aim of netbox is to be an IPAM solution for creating unique VPC CIDR blocks in AWS.

Issue
I've created a netbox IPAM prefix container of a /8 range thats been given to me by our netops dept. When I try and obtain a /22 child prefix from that /8 Ansible complains that this range is not a parent prefix.

When I use Terraform I get the next available /22 as I would expect. I can change the /8 prefix into a parent prefix and Ansible will get the next available /22. The reason I'd like to keep it as a container is you get the utilisation of child prefixes rolling up into the container prefix, which doesn't appear to be the case with parent parent prefixes.

Is there a way I can get the Ansible behaviour to be the same as terraform?

Thanks!