Add support for all new cloud models in Nautobot 2.3+

[tsm1th]

This is the start of the work needed to close issues: #373 #375 #371 #372 #374

• - Cloud Resource Type
• - Coud Service
• - Cloud Account
• - Cloud Network

The PR has a dependency and is directly related to nautobot/pynautobot#248 in the https://github.com/nautobot/pynautobot repo.

[tsm1th]

@joewesch - Starting this PR to spark a conversation about an issue I discovered. In the new cloud resources, a cloud_resource_type has a provider attribute which actually maps to a manufacturer. These are two very different things in Nautobot: circuits.provider and dcim.manufacturer. I ran into issues developing this new module because pynautobot is querying circuits.provider because of the "auto" discovery nature of nautobot-ansible.

You can see how I overcame this in the cloud.py module. I'm having to trick it by swapping those names around. I am hoping there is a better way, but this solution does work.

[joewesch]

@joewesch - Starting this PR to spark a conversation about an issue I discovered. In the new cloud resources, a cloud_resource_type has a provider attribute which actually maps to a manufacturer. These are two very different things in Nautobot: circuits.provider and dcim.manufacturer. I ran into issues developing this new module because pynautobot is querying circuits.provider because of the "auto" discovery nature of nautobot-ansible.

You can see how I overcame this in the cloud.py module. I'm having to trick it by swapping those names around. I am hoping there is a better way, but this solution does work.

We discussed this internally, but adding context here for transparency. I explained this sounds similar to how we dealt with name clashes in other modules. I suggested to review how we overcame this for location.parent (alias and key conversion)

[tsm1th]

Still need to add modules to support the many-to-many assignments.

• - Cloud Service Network Assignments
• - Cloud Network Prefix Assignments

[tsm1th]

This is complete and passing integration tests locally. Need PR approved and a release from pynautobot to update dependency for CI.

PYNAUTOBOT PR: nautobot/pynautobot#248

[tsm1th]

CI will pass once a patch is released in pynautobot and dependency is bumped. PR is submitted on that repo and awaiting approval: nautobot/pynautobot#253

[tsm1th]

Ok, got it now. Never use alternate name, use the alias instead. I should have got them all this time.