Feature #33789
Mark host where the installer is running as foreman when deploying foreman
Difficulty:
Triaged:
No
Related issues
Associated revisions
History
#1
Updated by Adam Ruzicka over 1 year ago
Updated by - Related to Tracker #32324: Distinguish between "regular" hosts and hosts on which Foreman and/or smart proxy runs added
#2
Updated by The Foreman Bot over 1 year ago
Updated by - Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/puppet-foreman/pull/965 added
#3
Updated by The Foreman Bot over 1 year ago
- Fixed in Releases 3.1.0 added
#4
Updated by Adam Ruzicka over 1 year ago
- Status changed from Ready For Testing to Closed
Applied in changeset puppet-foreman|8889aad54336f7e4b791665d6a58d3afd79e94f1.
Fixes #33789 - Mark host where the installer is running as foreman
when deploying foreman.
This introduces three new resources. foreman_host represents a host record in
Foreman. foreman_instance_host can be used to mark an already present
foreman_host as a foreman instance. foreman_smartproxy_host works similarly, but
marks an already present foreman_host as a host forming already existing
foreman_smartproxy.