Jira (PUP-4627) Storeconfigs unusable with Puppetserver
Title: Message Title Christopher Barbour commented on PUP-4627 Re: Storeconfigs unusable with Puppetserver This particular client is too large to continue using exported resources the way they currently are. Continued use of Active Record store configs is a stop-gap measure prior to moving to something else. So, this bug is less a question of "Do we continue using Active Record or migrate to PuppetDB?" and more a question of "Do we continue using Apache/Passenger/Rails/MRI Ruby or move to Puppetserver/Jruby?" Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4627) Storeconfigs unusable with Puppetserver
Title: Message Title Christopher Price commented on PUP-4627 Re: Storeconfigs unusable with Puppetserver I tend to agree with Henrik Lindberg's comments. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4627) Storeconfigs unusable with Puppetserver
Title: Message Title Henrik Lindberg assigned an issue to Eric Sorenson Puppet / PUP-4627 Storeconfigs unusable with Puppetserver Change By: Henrik Lindberg Assignee: Eric Sorenson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4627) Storeconfigs unusable with Puppetserver
Title: Message Title Christopher Barbour commented on PUP-4627 Re: Storeconfigs unusable with Puppetserver We'd be more than happy to supply a PR and update spec tests for the change, but before investing the effort I'd like to see if Puppet Labs is receptive to accepting a PR for Active Record against the 3.x or 3.8 branch. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4627) Storeconfigs unusable with Puppetserver
Title: Message Title Christopher Barbour created an issue Puppet / PUP-4627 Storeconfigs unusable with Puppetserver Issue Type: Bug Affects Versions: PUP 3.8.0 Assignee: Unassigned Created: 2015/05/18 11:58 AM Priority: Normal Reporter: Christopher Barbour The MySQL ruby gem will not compile for Jruby. As a result, current users of Active Record storeconfigs cannot upgrade to Puppetserver. The fix for this appears to be relatively straightforward; add jdbcmysql to the list of mysql connectors in the Puppet Rails library, and update the spec tests. The Active Record ORM should handle most of the complexity of using JDBC drivers, and the change poses no risk to users of the mysql and mysql2 connectors. https://github.com/puppetlabs/puppet/blob/3.x/lib/puppet/rails.rb https://github.com/puppetlabs/puppet/blob/3.x/lib/puppet/rails/database/schema.rb While storeconfigs are deprecated, this issue does block current users from moving away from Apache/Passenger/Rails. The requested change is simple, and extremely low risk.
