The hosts we are adding to Foreman have highly variable DNS assignments
because they are all DHCP, but we need to anchor the host's Foreman record
according to a strong convention.
When hosts get created in Foreman, the record name is derived from their
current DNS name.
In an environment such as ours, a host's DNS name is ephemeral.
Host A is created in Foreman with…
After the lease for Host A expires…
Host B is created in Foreman with…
DHCP: 192.168.2.1 (same)
FQDN: host-01.foo.com (same)
CERTNAME: puppet-node-02.bar.com (unique)
This causes inconsistencies and confusion.
Is it possible to create a foreman_hook to rename a host record according
to its certname?