Support to create Alias Records and Changing the State of a Pre-existing

[danpfe]

IP (for example if a previously created VM already took an address from
the DHCP pool).

[danpfe]

Hi guys, for some use-cases here at work we needed to be able to create alias records and change the state of a previously allocated IP address (such as the case where we created a VM that took its IP from a DHCP pool and then need to make it "DHCP_RESERVED"). Thought I'd contribute back the stuff I did and hope you find it useful.

[adarobin]

@danpfe I appreciate the PR! I like the alias record stuff, but I'm not 100% a fan of bluecat_ip4_change_state being a separate resource. I'm wondering if that logic should just be in bluecat_ip4_address and get rid of the ForceNew attribute from the action field.

[danpfe]

@adarobin I am absolutely willing to discuss the change_state resource, I know it's not "pretty" to have a resource that isn't really a resource; however: the reason I did it this way was because I didn't want to break the existing logic of "bluecat_ip4_address" for the use-case I described above (i.e. when it's not really "us" creating the IP in Terraform but it came into existance by being DHCP_ALLOCATED).