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

Enhancement: Install/upgrade from RPM/deb OS packages when compatible with target OS #7

Closed
maxmoser1 opened this issue Nov 23, 2020 · 4 comments
Assignees
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@maxmoser1
Copy link

Hi,

thanks for publishing this ansible role!

We noticed you use the tgz files regardless whether the target OS is supported by splunk's RPM or debian packages.
Would you be open for PR that uses ansible facts for detecting the target OS and use the packages instead of old raw tar files?

We prefer using RPM packages over tgz files whenever OS packages are available.

thanks!

@mason-splunk
Copy link
Contributor

@splunkenterprisecustomer Yes. Would you be contributing this, or are you asking us to develop it?

@mason-splunk mason-splunk self-assigned this Jan 19, 2021
@mason-splunk mason-splunk added the enhancement New feature or request label Jan 19, 2021
@maxmoser1
Copy link
Author

Here are the options we see in order of preference (option one would be preferred):

  1. you develop it (we are happy to beta test for RPM packages). (If this option is feasible, please let us know if you have a specific timeline in mind.)
  2. we contribute it via a pull request and it gets merged upstream into your repo and is maintained by you
  3. we develop it and it does not get merged (fork)

Would be great if you could share your thoughts on this.

@mason-splunk mason-splunk changed the title using RPM/deb OS packages when compatible with taraget OS Enhancement: Install/upgrade from RPM/deb OS packages when compatible with target OS Jan 26, 2021
@mason-splunk
Copy link
Contributor

The first option is possible but I can't provide a timeline for it. If you need this functionality sooner than later, I'd recommend submitting a PR for us to review.

That said, we opted to go with tarballs as they are cross-compatible across different Linux distros (e.g. Ubuntu vs RedHat). The latest version of Splunk is available in the .tgz files, not just .rpm and .deb packages, so I'm not sure what you mean by "old raw tar files".

@mason-splunk
Copy link
Contributor

After further consideration, this is not something we will be implementing. The workflows for this role are fairly sophisticated/mature and the risk of breaking functionality in the role by attempting to incorporate RPM/DEB is high, while the ROI is low.

If you can identify any specific requirements that this role does not meet using TGZ files but are met using RPM/DEB packages, I would be interested in learning more. However, we believe the current implementation using TGZ files is the best one given the information we have today.

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

No branches or pull requests

2 participants