Jira (PUP-9004) Spike hiera 3 removal
Title: Message Title Nick Walker commented on PUP-9004 Re: Spike hiera 3 removal Josh Cooper should we be considering this for Puppet 7? Is there anything we'd want to do to further highlight the deprecation of hiera 3 and get users onto hiera 5? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9004) Spike hiera 3 removal
Title: Message Title Josh Cooper commented on PUP-9004 Re: Spike hiera 3 removal I wanted to understand the relationship between puppet and hiera, seeing as how hiera 5 is implemented entirely in puppet. Now that we have some clarity, and the fact that we already agree to that it's too soon to remove hiera3 support, I'm closing this as won't do. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9004) Spike hiera 3 removal
Title: Message Title Henrik Lindberg commented on PUP-9004 Re: Spike hiera 3 removal I suggested removing the hiera CLI as a minimum. Nothing depends on that except users that still use it instead of lookup. Some may find lookup more difficult because there is not REST version of it. We may want to add that so it is possible to do lookups from an agent (limited to that agent). Removing the hiera_xxx functions is too soon IMO. They have never been aliased to lookup, you have to do that manually as the semantics are not 100% compatible (i.e. you stick a couple of small puppet language functions in your site.pp to override the built in hiera functions. Removing the hiera CLI will remove one confusion for users as it simply does not work well, and has zero support for hiera 5. The thing next up is to force users to use hiera 5 hiera.yaml while still supporting hiera 3 backends. This simply pushes people towards making the transition. I think it is too soon to drop hiera 3 altogether since that will surely break some users that cannot use custom backends. If we want to be more radical, we would stop shipping hiera 3 gem. Users who need it will need to install it. That means that anyone using a hiera 3 backend would most likely have to install the gem as logic in hiera 3 backends typically depend on the gem. Maybe this is still a good step to take - while it is uncomfortable, maybe it will drive people towards requesting hiera 5 support for custom backends they use. (I know some backends support both 3 and 5 - they may still break because they may be have logic that gets loaded that require the hiera 3 gem to be present). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9004) Spike hiera 3 removal
Title: Message Title Nick Walker commented on PUP-9004 Re: Spike hiera 3 removal Does this include removal of the hiera function or will that still redirect to lookup? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9004) Spike hiera 3 removal
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9004 Spike hiera 3 removal Change By: Josh Cooper Team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9004) Spike hiera 3 removal
Title: Message Title Josh Cooper created an issue Puppet / PUP-9004 Spike hiera 3 removal Issue Type: Task Assignee: Unassigned Created: 2018/07/13 11:01 AM Priority: Normal Reporter: Josh Cooper From Henrik Lindberg: The hiera 3 CLI can be removed without side effects. Removing hiera gem from packaging can break hiera 3 backends as they may be reusing code in the hiera gem - naturally, just dropping the dependency will require that users install the hiera 3 gem. We could do a "sleep number_of_days_since_6_0" to make hiera 3 go slower and sloower and slooower How many hiera 3 backends are there that haven't been converted to hiera 5. For example, https://github.com/crayfishx/hiera-mysql is hiera5 based. Add Comment
