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

Remove pluginsync setting if upgrading to 1.4.x #97

Closed
wants to merge 1 commit into from

Conversation

tphoney
Copy link
Contributor

@tphoney tphoney commented Mar 29, 2016

No description provided.

@tphoney tphoney changed the title Remove pluginsync setting if upgrading to 1.4.x {WIP} Remove pluginsync setting if upgrading to 1.4.x Mar 29, 2016
@tphoney tphoney force-pushed the pe-14495 branch 4 times, most recently from 4782f66 to 2ac6a6e Compare March 29, 2016 15:57
@@ -26,7 +26,14 @@
# Deprecated for global config
'config_version', 'manifest', 'modulepath',
# Settings that should be reset to defaults
'disable_warnings', 'vardir', 'rundir', 'libdir', 'confdir', 'ssldir', 'classfile'].each |$setting| {
'disable_warnings', 'vardir', 'rundir', 'libdir', 'confdir', 'ssldir', 'classfile']
Copy link
Contributor

Choose a reason for hiding this comment

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

Indentation looks off.

@tphoney tphoney force-pushed the pe-14495 branch 2 times, most recently from 45283f5 to ec0228e Compare March 29, 2016 16:56
@highb
Copy link
Contributor

highb commented Mar 29, 2016

This will only cleanup the settings on upgrades from <= 3.8 (see prepare.pp)

@MikaelSmith
Copy link
Contributor

Oh yeah... might need another class to cover new deprecations.

'disable_warnings', 'vardir', 'rundir', 'libdir', 'confdir', 'ssldir', 'classfile'].each |$setting| {
'disable_warnings', 'vardir', 'rundir', 'libdir', 'confdir', 'ssldir', 'classfile']
# When upgrading to 1.4.x or later remove pluginsync
if versioncmp($::puppet_agent::package_version, '1.4.0') >= 0 {
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor

Choose a reason for hiding this comment

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

We should also handle undef. If we get this far with undef, it means we're updating to FOSS latest, so we should also remove pluginsync in that case.

@tphoney
Copy link
Contributor Author

tphoney commented Apr 4, 2016

@MikaelSmith @highb I made the suggested changes. Sorry for the ping pong nature of this.

@MikaelSmith
Copy link
Contributor

This needs a rebase now, and you could remove the WIP note.

@tphoney tphoney changed the title {WIP} Remove pluginsync setting if upgrading to 1.4.x Remove pluginsync setting if upgrading to 1.4.x Apr 4, 2016
@MikaelSmith
Copy link
Contributor

👍

@MikaelSmith
Copy link
Contributor

Oh, should probably add a spec. I'll add it and put up a new PR.

@MikaelSmith MikaelSmith closed this Apr 5, 2016
@MikaelSmith
Copy link
Contributor

Put up a new PR at #101.

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

Successfully merging this pull request may close these issues.

3 participants