Skip to content
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

Enable strict #71

Closed
wants to merge 2 commits into from
Closed

Enable strict #71

wants to merge 2 commits into from

Conversation

mterzo
Copy link

@mterzo mterzo commented Jun 26, 2016

This is go on top of the travis changes to do more strict testing.

mterzo and others added 2 commits June 25, 2016 20:28
chaning a few test cases to define factor values
adding udnef trapd damemon name for debian
@mterzo
Copy link
Author

mterzo commented Jun 27, 2016

Fixes #65

@walkamongus
Copy link

+1 -- getting these errors as well

@cdenneen
Copy link

cdenneen commented Sep 6, 2016

@razorsedge any eta on merging this?

@mterzo
Copy link
Author

mterzo commented Sep 7, 2016

@razorsedge, do you want to continue to maintain this module?

@razorsedge
Copy link
Contributor

@mterzo, What I want and what my two young children demand are presently in conflict. :-( Needless to say, when I have the time I don't have the energy and when I have the energy, I don't have the time.

As for this PR, I see a few issues:

  1. I use modulesync for the .travis.yml. Edit .sync.yml for any overrides.
  2. Please read through the DEVELOP.md file. It will tell you to branch from develop and not master.
  3. Fact ::operatingsystemmajrelease does not exist in all versions of Puppet that this module supports.
  4. But mainly, params.pp is never a parameterized class. If the world needs strict_variable support, PR Support strict_variables by removing dynamic lookups #21 is going to be the way to do it.

@razorsedge razorsedge self-assigned this Sep 7, 2016
@razorsedge razorsedge added the enhancement New feature or request label Sep 7, 2016
@mterzo
Copy link
Author

mterzo commented Sep 7, 2016

We all have busy lives.

I honestly don't know what I was thinking.

We need to get strict support for puppet 4. I'll rework it this a bit and resubmit.

@mterzo mterzo closed this Sep 7, 2016
@cdenneen
Copy link

cdenneen commented Sep 7, 2016

@mterzo I would probably use puppetlabs/ntp as example and not parameterize the params class.
@razorsedge thanks for the update, I don't think anything was meant by the question, also with so many modules moving over to the voxpupuli namespace, I think lately all public modules are starting to be asked this a lot. Allows for you to maintain it still but gives you help as well.

@razorsedge
Copy link
Contributor

@mterzo @cdenneen No worries. I've had a pretty horrible year with all sorts of life events. I look at my growing mountain of PRs and issues and don't know where to start. I did seriously consider donating to Puppet Community/voxpupuli when they were first created.

@mterzo
Copy link
Author

mterzo commented Sep 7, 2016

They so good work. It would definitely help with keeping the dependencies up-to-date. I checked out voxpupuli's msync and they have dropped support for older versions of ruby.

@mterzo
Copy link
Author

mterzo commented Sep 7, 2016

@cdenneen I thought I had followed ntp and others. i think I cherry-picked the wrong commit. When making the branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants