This repository has been archived by the owner on Jul 3, 2024. It is now read-only.
Make puppet environment optional. #73
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
In case anyone tries to google the error message I got when trying to create a host after puppet was removed, here it is: |
…ate option appears in the GUI
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Foreman no longer requires puppet to manage hosts. In fact, it is possible to purge puppet completely from a foreman installation (see https://docs.theforeman.org/3.1/Managing_Configurations_Puppet/index-katello.html#Disabling_Puppet_Integration_managing-configurations-puppet ) which is what I have done. Doing so breaks VM creation.
This patch makes the puppet environment variable optional. I'm not sure why the environment was required or used before, but I haven't noticed any ill effects yet.