Closed
Bug 918070
Opened 12 years ago
Closed 12 years ago
Upgrade eyaml so -p works
Categories
(Infrastructure & Operations :: RelOps: Puppet, task)
Infrastructure & Operations
RelOps: Puppet
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
Details
Attachments
(1 file)
|
4.29 KB,
patch
|
rail
:
review+
|
Details | Diff | Splinter Review |
https://github.com/TomPoulton/hiera-eyaml/pull/12
so this should work in 1.3.1; we're using an older version. This just needs to be re-packaged.
|
Assignee | |
Updated•12 years ago
|
Assignee: nobody → dustin
|
|
Assignee | |
Comment 1•12 years ago
|
||
I tried 1.3.4 and it seems incompatible. I'll see what other changes are required to make that compatible.
|
|
Assignee | |
Comment 2•12 years ago
|
||
In fact, it seems to have some pretty serious bugs:
https://github.com/TomPoulton/hiera-eyaml/issues/30
https://github.com/TomPoulton/hiera-eyaml/issues/31
so we'll wait until those get resolved.
|
|
Assignee | |
Comment 3•12 years ago
|
||
2.0.0 seems to fix this. I'll try it out in relabs.
|
|
Assignee | |
Comment 4•12 years ago
|
||
tested in relabs
Attachment #8348925 -
Flags: review?(bugspam.Callek)
|
||
Updated•12 years ago
|
Attachment #8348925 -
Flags: review?(bugspam.Callek) → review+
|
|
Assignee | |
Comment 5•12 years ago
|
||
The old ensure => latest meant that everything upgraded hiera-eyaml once I landed it in the repo, which caused bustage :(
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•