-
-
Notifications
You must be signed in to change notification settings - Fork 168
initial modulesync #174
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
initial modulesync #174
Conversation
@bastelfreak @rnelson0 I need some help here to get tests pass:
Would be great to get this PR merged soon so we can cut a first official Forge release under the Vox Pupuli umbrella. Thanks for any help |
Fixes via rubocop -a
|
@walterheck Yes, this will happen in #173 @rnelson0 @bastelfreak Would be very great if we could proceed here. Any ideas how to get the failing tests fixed? |
The puppet error is pretty simple, use a The rubocop ones are more tedious. You can probably run |
We should get this merged and don't spend too much time on rubocop warnings in spec files. IMO it's okay to disable the specific cops in the spec files that can't be autofixed - at least for now. |
Update for rubocop compliance
Now the only failing check:
Does anyone have the possibility to fix this? |
Ensure spec test use hiera fixtures.
This is the first modulesync run: