-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove _module from apache::mod::unique_id name. #2339
remove _module from apache::mod::unique_id name. #2339
Conversation
apache::mod::security is a classthat may have no external impact to Forge modules. This module is declared in 175 of 579 indexed public
|
@mdklapwijk Look's like this change is causing some failures in the unit tests. |
@david22swan, the reason is partly about consistency througout this module:
But mostly about it resulting into the module enabled twice under certain conditions:
|
I have no idea why those 2 spec tests are failing, as they only state
|
00881da
to
cd9673b
Compare
We actually have multiple rspec processes running in parallel and they all report their failures separate. It's a trade off between performance and usefulness. puppetlabs/puppetlabs_spec_helper@8eaa209 should make it easier to see in CI, but is currently unreleased. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Reason behind the change seems logical to me and everything is green so happy to merge.
The unique_id module gets installed/loaded with its internal id 'unique_id_module' used as name; resulting in inconsistent naming and possible double entries if the module was already enabled outside of puppet (or security.pp).