Ability for user to augment plan with self maintained DNS module

[ody]

Use Case

To install Puppet Enterprise with organization specific DNS additional cloud configuration alongside what we provide in our open source Terraform modules is required

Example:

User populates a specific DNS zone with the names of infrastructure nodes and uses those names as the configuration items that tie together the communication fabric of PE

Describe the Solution You Would Like

Autope execute of user provided module between the initial provisioning and execution of peadm to export provisioned infrastructure names to a custom DNS zone

Example:

After pe_arch runs and constructs an inventory, user provided module configures custom DNS zone with host names based on provisioned instances using constructed inventory, FQDN using custom domain is passed to peadm instead of cloud provided FQDN

Describe Alternatives You've Considered

User modifies and maintains a forked version of pe_arch modules

Additional Context

More research could be done to determine if this flow works for more than the specific use case. Example is derived from real conversation with user and is meant to facilitate puppetlabs/terraform-aws-pe_arch#11 but might work for other modificaitons which are unrelated to DNS. Multi-staged provisioning in autope is yet to be designed...

[davidsandilands]

@ody is this still relevant due to age?