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

Update Package version #262

Closed
rwaffen opened this issue Jun 18, 2020 · 2 comments
Closed

Update Package version #262

rwaffen opened this issue Jun 18, 2020 · 2 comments

Comments

@rwaffen
Copy link
Sponsor Member

rwaffen commented Jun 18, 2020

Hallo Community,

would it be a good idea to be able to update the icingaweb2 package via puppet/hiera?
Is there a explicit reason to only set it to "installed"?

https://github.com/Icinga/puppet-icingaweb2/blob/ba81a9a01ed8aeb5fea14c6ec5e855e7f8c794e3/manifests/install.pp#L14-L18

@lbetz
Copy link
Contributor

lbetz commented Jun 19, 2020

Hi Robert,

taht's not the best idea. Puppet is a configuration management tool, software management should be done by other tools like katello, spacewalk, ... or a simple repository and maybe in cooperation with orchestration tools.

Updating software could be a complex process, icingaweb for example has package dependency and optional a database with a schema that could be changed thru an update.

If you really wanna do an update with puppet set manage_package to false and do the package management yourself via resource package before declaring the class icingaweb2.

Bye
Lennart

@rwaffen
Copy link
Sponsor Member Author

rwaffen commented Jun 19, 2020

Hi Lennart,

Thought it might be a good idea because in many other modules you can handle the package version internally. But when this is your (team) design decision, than it is set.

I will go with the manage_package option and manage the version on myself. I like the option to pin/install/update versions in my hiera data.

But thanks for the clarifications.

Greetings.

@lbetz lbetz closed this as completed Aug 31, 2020
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

No branches or pull requests

2 participants