Thanks for the updates. To answer your question from earlier as to why i never put it in the forge, it was mainly time and priorities. I needed to be able to support it completely in ci in my current infra which is mainly dedicated to OpenStack on Windows. We currently are tied (according to Canonical) as the largets maas deployment in the world. ;) So thanks again. I do also know there were some package name changes w/ maas 2.0 that I haven't accounted for yet as well.
Thanks for the updates. To answer your question from earlier as to why i never put it in the forge, it was mainly time and priorities. I needed to be able to support it completely in ci in my current infra which is mainly dedicated to OpenStack on Windows. We currently are tied (according to Canonical) as the largets maas deployment in the world. ;) So thanks again. I do also know there were some package name changes w/ maas 2.0 that I haven't accounted for yet as well.