Skip to content
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.

Initial support for puppetserver 2.0.0 paths #8

Merged
merged 1 commit into from
Jul 9, 2015

Conversation

roman-mueller
Copy link
Member

Puppetserver 2.0.0 uses the path /etc/puppetlabs/puppetserver/* now for its configuration files.
This PR adds support for this.
I'm dislike checking for $::puppetversion but there is no fact for the the puppetserver version.
If you have a better way of checking this, I'm happy to hear it.

@@ -4,7 +4,11 @@
) {
require ::puppetserver::augeas

$targetdir = '/etc/puppetserver/conf.d'
if versioncmp($::puppetversion, '4.0.0') >= 0 {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm surprised this is linked to $::puppetversion

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@raphink Well, see my initial comment in the PR.
It's not linked, but I don't know a better way to make the decision here, there is no $::puppetserverversion...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess this module would be a proper place to ship such a fact then.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@raphink I guess it's safe to admit that if puppetversion >= 4.0.0 than we use puppetserver 2.x, so I'm not sure that we need (yet) another fact which will not be available at first run.

mcanevet added a commit that referenced this pull request Jul 9, 2015
Initial support for puppetserver 2.0.0 paths
@mcanevet mcanevet merged commit 2bb33f9 into voxpupuli:master Jul 9, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants