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

WIP: Add upgrade/version handling for splunkforwarder #164

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

arjenz
Copy link
Member

@arjenz arjenz commented Dec 7, 2017

This allows upgrading splunkforwarder by bumping version/build passed to this module. As a workaround more or less for #125.

Changing the version/build parameters to splunk::params results in:

Notice: /Stage[main]/Splunk::Forwarder/Package[splunkforwarder]/ensure: ensure changed '6.5.1-f74036626f0c' to '6.6.2'

Only implemented for splunkforwarder and tested on CentOS right now. If there's interest I can expand it to support splunk and test on other distributions.

  • Change "ensure" to an explicit version (otherwise only the file in /opt/staging will be added when $version is bumped)
  • Extra handling of accepting the license

ensure => absent for the ftr file might even completely replace Exec['license_splunkforwarder'] eventually (untested, however)

@bastelfreak bastelfreak added the enhancement New feature or request label Dec 9, 2017
@bastelfreak
Copy link
Member

Hi @arjenz, thanks for the PR. Can you take a look at the failing travis jobs?

@bastelfreak bastelfreak added the needs-work not ready to merge just yet label Dec 9, 2017
@arjenz
Copy link
Member Author

arjenz commented Dec 12, 2017

@bastelfreak It will only ensure a version on RedHat now, and rebased with latest master.

The 'apt' provider is versionable, but 'dpkg' is not (which is being used here). apt also can install dpkg files directly on more recent versions, but not sure if that's exposed through puppet.

@arjenz arjenz force-pushed the upgrade branch 4 times, most recently from a764ccf to 143d97a Compare December 13, 2017 13:32
@kenmaglio
Copy link

Just as a note, we've noticed the exec virtual resource won't be realized on an upgrade, as the file (/opt/splunkforwarder/etc/auth/server.pem) continues to exist between upgrades. Since this modification isn't removing that file as well, then this would never allow the exec to fire.

- Change "ensure" to an explicit version (otherwise only the file in /opt/staging will be added when $version is bumped)
- Extra handling of accepting the license
- Limit `ensure => version` to RedHat, the 'dpkg' provider is not versionable, so only specify version on osfamily RedHat.
@vox-pupuli-tasks
Copy link

Dear @arjenz, thanks for the PR!

This is pccibot, your friendly Vox Pupuli GitHub Bot. I noticed that your pull request contains merge conflict. Can you please rebase?

You can find my sourcecode at voxpupuli/vox-pupuli-tasks

1 similar comment
@vox-pupuli-tasks
Copy link

Dear @arjenz, thanks for the PR!

This is pccibot, your friendly Vox Pupuli GitHub Bot. I noticed that your pull request contains merge conflict. Can you please rebase?

You can find my sourcecode at voxpupuli/vox-pupuli-tasks

@vox-pupuli-tasks
Copy link

Dear @arjenz, thanks for the PR!

This is pccibot, your friendly Vox Pupuli GitHub Bot. I noticed that your pull request contains merge conflict. Can you please rebase?

You can find my sourcecode at voxpupuli/vox-pupuli-tasks

@vox-pupuli-tasks
Copy link

Dear @arjenz, thanks for the PR!

This is pccibot, your friendly Vox Pupuli GitHub Bot. I noticed that your pull request contains merge conflict. Can you please rebase?

You can find my sourcecode at voxpupuli/vox-pupuli-tasks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request merge-conflicts needs-work not ready to merge just yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants