Disable EPEL by default, get GPG key via URL #23
Merged
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.
If an existing system has not been deployed with EPEL repositories, then
the EPEL GPG key will not be present on the system. Enabling EPEL
repositories using a file-based GPG key would then fail, and break
subsequent DNF commands. Specify the EPEL GPG key via URL to avoid this
issue when EPEL is enabled. Allow the URL to be configured via
dnf_epel_gpg_key_url for air-gapped environments.
EPEL is no longer required for a default installation. Let's stop
installing epel-release by default by setting dnf_install_epel to false.
Also, add a new dnf_enable_epel variable that defaults to the value of
dnf_install_epel, and determines whether EPEL repositories will be
enabled on hosts.