cloud-init should have generic mechanism for installing specific package versions
Bug #1108047 reported by
Craig Tracey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
Low
|
Craig Tracey |
Bug Description
As it stands right now, the only way to install specific package versions (ie. puppet-3.0.2) is to specifically call out the correct package format by distro. For example, yum would want puppet-3.0.2 whereas apt would like puppet=3.0.2. This would force any config module writer to explicitly fork logic on distro if they intend to support versions.
Related branches
lp:~craigtracey/cloud-init/package-versions
- Joshua Harlow: Pending requested
-
Diff: 192 lines (+68/-15)7 files modifiedcloudinit/config/cc_landscape.py (+1/-1)
cloudinit/config/cc_puppet.py (+8/-2)
cloudinit/config/cc_salt_minion.py (+1/-1)
cloudinit/distros/debian.py (+13/-4)
cloudinit/distros/rhel.py (+12/-4)
cloudinit/util.py (+29/-3)
doc/examples/cloud-config-install-packages.txt (+4/-0)
Changed in cloud-init: | |
assignee: | nobody → Craig Tracey (craigtracey) |
To post a comment you must log in.
fixed in trunk at revno 776.