Fix CRD group name not following conventions

[faebr]

• Changed domain to netboxlabs.com
• Changed group to ipam
• Adapted api paths and crd group to convention: ipam.netboxlabs.com
• Thought about changing pkg/netbox to pkg/ipam but after starting the change, realized that there is for example ipam.go in models and lots of names containing netbox in this pkg so probably confusing to change, so currently left it like this. Any thoughts on this?

[henrybear327]

Note: merge only after 0.0.1-alpha.1 is released!

[jstudler]

Why netboxlabs.com and not netbox.dev? NetBox Labs is the company and not the community, this project is hosted on the community.

[faebr]

Why netboxlabs.com and not netbox.dev? NetBox Labs is the company and not the community, this project is hosted on the community.

@jstudler, the netbox.dev domain is not mentioned when looking at the github, but only netboxlabs.com. Also @rboucher-me mentioned this would be their preference when asked. Those were the 2 main reasons.

[henrybear327]

We will make another release after this is merged, as this is a breaking change

[henrybear327]

After some discussions on Slack, we decided that we would prefer to stick with the netbox.dev domain.

The main reasons are

• the NetBox-operator is built for NetBox, thus, netbox.dev is a clearer indication of what this project is built for
• the NetBox-Operator is not related to netboxlabs.com

[henrybear327]

LGTM! Thanks @faebr

[henrybear327]

@faebr please resolve the rebase conflict :( Thanks!

[henrybear327]

The PR base has been changed to #74. More conflicts to resolve :( @faebr

New discussion requiring new changes

[henrybear327]

@MaIT-HgA do you want to rebase this PR and make it ready for merging :)

[MaIT-HgA]

@MaIT-HgA do you want to rebase this PR and make it ready for merging :)

done :)

[henrybear327]

Thanks @MaIT-HgA for rebasing it!

As discussed during the meeting, we have decided to postpone the merging of this PR, as this would require migration to be done for the existing CRs and it's currently de-scoped from our development sprint.

[faebr]

This PR will be closed, an easier solution has been found. We will remove the crd group from the PROJECT file and thus the already created crd's are alligned again. New crd's can be added without a group or inside a new group after enabling multi-group support in the said file.