Fix issue when using apache2_mod_ssl resource instead a wrapper resource#800
Merged
Fix issue when using apache2_mod_ssl resource instead a wrapper resource#800
Conversation
When doing `apache2_module 'ssl'` instead of another custom resource, the mod_ssl package does not get installed properly due to the fact it's set to run in the root context of the chef run. However, it never seems to get installed, or at least installed in time for it to work leaving a system in a broken state. I cannot see why this was needed in the first place as it seems to work without it. Signed-off-by: Lance Albertson <lance@osuosl.org>
mvangoor
approved these changes
Oct 19, 2023
bmhughes
approved these changes
Oct 20, 2023
Contributor
|
Released as: 9.0.6 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When doing
apache2_module 'ssl'instead of another custom resource, themod_ssl package does not get installed properly due to the fact it's set to run
in the root context of the chef run. However, it never seems to get installed,
or at least installed in time for it to work leaving a system in a broken state.
I cannot see why this was needed in the first place as it seems to work without
it.
Signed-off-by: Lance Albertson lance@osuosl.org
Description
Describe what this change achieves
Issues Resolved
List any existing issues this PR resolves
Check List
## Unreleased