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

Refactor highline import #187

Merged
merged 4 commits into from
Mar 2, 2016
Merged

Conversation

petems
Copy link
Member

@petems petems commented Feb 24, 2016

Refactoring Utils class, moving all methods into separate domain specific helper classes. The main aim is to fix the memory leaks caused by highline (#163).

@cprice404
Copy link

Reviewed this; at a glance it LGTM and seems like it should avoid the 'highline' import for the server/decrypt code paths, but I haven't run it.

@petems
Copy link
Member Author

petems commented Feb 26, 2016

Tested and working in my example, more details here: https://tickets.puppetlabs.com/browse/SERVER-1154

I think a bump to the Gemspec to change the Highline version would also be good, will do a seperate PR for that 😄

@petems
Copy link
Member Author

petems commented Feb 27, 2016

@sihil would it be possible to have this merged after the Travis CI checks have been merged and the RC1 gem tested? In our test this fixes the memory leak issues in Puppet Server as seen in #163.

@sihil
Copy link
Collaborator

sihil commented Feb 27, 2016

@petems I was wondering if that would be desirable or not. Would you suggest merging both this and #181 into the same release?

@petems
Copy link
Member Author

petems commented Feb 27, 2016

@sihil I just did a build on travis with this branch with #181 branch merged in and a bunch of tests failed, so let me fix those first.

@petems
Copy link
Member Author

petems commented Feb 27, 2016

OK, tests now passing, it caught some issues I'd missed: https://travis-ci.org/petems/hiera-eyaml/builds/112290675 👍

@sihil
Copy link
Collaborator

sihil commented Feb 28, 2016

@petems - thanks for fixing the tests. I've cut and pushed 2.1.0.rc2 with this fix in. As per #181 - I don't have access to testing infrastructure so would appreciate others giving a 👍 to 2.1.0.rc2. Will merge and cut 2.1.0 once there is a reasonable level of confidence.

As an aside I noticed on the ticket that there were discussion of puppetlabs officially supporting hiera-eyaml. I think that's probably not a bad idea. I can't speak for @TomPoulton or @gtmtech but personally I no longer use hiera-eyaml so don't have the same level of enthusiasm or time for the project. At the very least it makes sense to me that some puppetlabs folks have push access to this repo and are added as owners to the rubygem. Similarly - I don't know about usage of hiera-eyaml-gpg but I'm very happy to add people to that (or hand over the repo) if you are also finding yourselves supporting that.

@petems
Copy link
Member Author

petems commented Feb 29, 2016

@sihil Getting people from Puppetlabs to have commit-bit would be awesome, and I'm sure we could get some eyes on the number of PR's and issues. @TomPoulton and @gtmtech do you have any objections? Maybe even a move to Voxpupuli?

I've seen a few that should be fairly good to merge ASAP (#157, https://github.com/TomPoulton/hiera-eyaml/pull/144/files) then some others that might need a major version bump.

@petems
Copy link
Member Author

petems commented Feb 29, 2016

@sihil Also, I've just tested and 2.1.0.rc2 works fine in my test environment, I'm 👍 for an official release.

sihil added a commit that referenced this pull request Mar 2, 2016
@sihil sihil merged commit 97c71dd into voxpupuli:master Mar 2, 2016
@sihil
Copy link
Collaborator

sihil commented Mar 2, 2016

@petems Cut 2.1.0 and pushed to world. Thanks for helping testing.

We've been having some e-mail discussion - hopefully @TomPoulton will add a bunch of you guys in the near future.

@petems
Copy link
Member Author

petems commented Mar 2, 2016

Awesome, thanks! 😄

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

Successfully merging this pull request may close these issues.

None yet

3 participants