Jira (PUP-4380) Split non-core puppet functionality into modules
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Josh Cooper Epic Status: To Do Done 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-4380) Split non-core puppet functionality into modules
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Josh Cooper Sub-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-4380) Split non-core puppet functionality into modules
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Josh Cooper Team/s: Platform Core 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-4380) Split non-core puppet functionality into modules
Title: Message Title Kenn Hussey assigned an issue to Josh Cooper Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Kenn Hussey Assignee: Josh Cooper 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-4380) Split non-core puppet functionality into modules
Title: Message Title Craig Gomes updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Craig Gomes To reduce the surface area of puppet itself and increase maintainability of non-core puppet, things which can be split out from it should be. Prime examples include the Nagios types (Redmine #4146 / [ PUP-1077 ] ) and some of the more esoteric single-OS types/providers like solaris zpools. These could still be combined at packaging time but the puppet repository itself would not contain them.Spreadsheet of Non-core types and providers: [ https://docs.google.com/spreadsheets/d/1QttzO2-93TTejx2ifKCxmfhW3qmhg-gaaxvgoRymRHk/edit#gid=0 |https://docs.google.com/spreadsheets/d/1T1S2BWQ_S0J0NywTTHNJuONWYYopDqtxChsom4-avD4/edit#gid=0] 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
Jira (PUP-4380) Split non-core puppet functionality into modules
Title: Message Title Henrik Lindberg commented on PUP-4380 Re: Split non-core puppet functionality into modules We pre-populate the 4.x loaders with known resource types. When types are extracted should be remove them from pre-loading? From a strict standpoint puppet core can not know they exist so it should not pre-load them (if they were one day excluded from the packaging the name would also need to be removed). From a safety-rails perspective it is good that they are still present to avoid someone creating a non resource data type with the same name (which is impossible when they are pre-loaded). 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-4380) Split non-core puppet functionality into modules
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Kenn Hussey Due Date: 2018/ 09 05 / 19 16 Priority: Major Critical 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-4380) Split non-core puppet functionality into modules
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Josh Cooper Epic Colour: ghx-label-2 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-4380) Split non-core puppet functionality into modules
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Josh Cooper Sub-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-4380) Split non-core puppet functionality into modules
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Kenn Hussey Due Date: 2018/09/19 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-4380) Split non-core puppet functionality into modules
Title: Message Title Craig Gomes updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Craig Gomes To reduce the surface area of puppet itself and increase maintainability of non-core puppet, things which can be split out from it should be. Prime examples include the Nagios types (Redmine #4146 / [PUP-1077]) and some of the more esoteric single-OS types/providers like solaris zpools. These could still be combined at packaging time but the puppet repository itself would not contain them. Spreadsheet of Non-core types and providers: https://docs.google.com/spreadsheets/d/1QttzO2-93TTejx2ifKCxmfhW3qmhg-gaaxvgoRymRHk/edit#gid=0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-4380) Split non-core puppet functionality into modules
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Geoff Nichols Team/s: Agent Platform Core Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-4380) Split non-core puppet functionality into modules
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Moses Mendoza Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-4380) Split non-core puppet functionality into modules
Title: Message Title John Duarte updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: John Duarte Team/s: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-4380) Split non-core puppet functionality into modules
Title: Message Title John Duarte updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: John Duarte Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-4380) Split non-core puppet functionality into modules
Title: Message Title Geoff Nichols commented on PUP-4380 Re: Split non-core puppet functionality into modules Retargeted this to PUP 6.0. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-4380) Split non-core puppet functionality into modules
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Geoff Nichols Fix Version/s: PUP 5.y Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-4380) Split non-core puppet functionality into modules
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Geoff Nichols Business Value: 452 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-4380) Split non-core puppet functionality into modules
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Kenn Hussey Fix Version/s: PUP 5.0.0 Fix Version/s: PUP 5.y Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-4380) Split non-core puppet functionality into modules
Title: Message Title Eric Sorenson commented on PUP-4380 Re: Split non-core puppet functionality into modules Moses Mendoza i would love to see this in puppet 5, especially since there's been a lot of conversation and relatively concrete proposals put forth. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-4380) Split non-core puppet functionality into modules
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Moses Mendoza Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-4380) Split non-core puppet functionality into modules
Title: Message Title Moses Mendoza commented on PUP-4380 Re: Split non-core puppet functionality into modules We talked about this epic as a potential candidate for PUP 5.0. Is this still relevant/of high enough value to consider for that Eric Sorenson? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-4380) Split non-core puppet functionality into modules
Title: Message Title Eric Sorenson commented on PUP-4380 Re: Split non-core puppet functionality into modules I flipped that spreadsheet's permissions to public. 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-4380) Split non-core puppet functionality into modules
Title: Message Title Kylo Ginsberg commented on PUP-4380 Re: Split non-core puppet functionality into modules This spreadsheet: https://docs.google.com/a/puppetlabs.com/spreadsheets/d/1QttzO2-93TTejx2ifKCxmfhW3qmhg-gaaxvgoRymRHk/edit#gid=0 is a very rough draft at what we might split out. Where there was clear consensus in the puppet-dev threads linked above, I followed that. But that left details open for discussion, and I made a best effort at good judgment there, but there's room to discuss. So chime in on the spreadsheet. /cc 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-4380) Split non-core puppet functionality into modules
Title: Message Title Eric Sorenson commented on PUP-4380 Re: Split non-core puppet functionality into modules Justin Stoller yes, I envision there being two possible destinies for the modules thus extracted: supported module - goes to puppetlabs namespace - probably not to the module eng team as they mostly work on application modules like puppetlabs-mysql and these are kind of categorically different, so it seems unreasonable to put that burden on them. approved module - goes to puppetlabs-community namespace - these would be more OS-specific types and providers that make sense to open up commit access, such as the Mac OS X and *BSD providers. 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-4380) Split non-core puppet functionality into modules
Title: Message Title Justin Stoller commented on PUP-4380 Re: Split non-core puppet functionality into modules Kylo Ginsberg, Eric Sorenson, just to clarify, the MVP for this in the SG timeframe is not to simply module-ify nagios within the puppet code base, but to remove it from the code base and transition it to being a supported module (supported by either the module or client team)? 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-4380) Split non-core puppet functionality into modules
Title: Message Title Kylo Ginsberg commented on PUP-4380 Re: Split non-core puppet functionality into modules I just had separate conversations with Eric Sorenson and Matthaus Owens and my takeway is captured below (note that this is slightly different than what Justin Stoller described above): The plan for any identified modules (currently just nagios) is: that code is removed from github.com/puppetlabs/puppet a module is created in either the puppet-community or puppetlabs namespace that module is either Approved (if in the puppet-community namespace) or Supported (if in the puppetlabs namespace) that module is packaged into AIO based on a vanagon component in puppet-agent (which would specify the release of the module) One prerequisite for this: puppet-agent repo is OSS so that community members can view and PR against it. 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-4380) Split non-core puppet functionality into modules
Title: Message Title Justin Stoller commented on PUP-4380 Re: Split non-core puppet functionality into modules Also, to provide info to the question I raised, I believe elsewhere Eric Sorenson set the initial scope of this (Puppet 4.2 timeframe) to include organizing the types and providers internally as modules so they are pulled down via filesync. Though they continue to be in tree and maintained by PL they otherwise look like modules. Then through the PUP 4 lifetime they would be moved to community namespace or wherever. I still have a feeling that the wherever for PE support through the 4.x lifecycle will mean some kind of collaboration with the supported modules team. But that decision doesn't need to be made now. Kylo Ginsberg, are the core/external types going to be documented somewhere, like an arm? 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-4380) Split non-core puppet functionality into modules
Title: Message Title Kylo Ginsberg commented on PUP-4380 Re: Split non-core puppet functionality into modules For context on what we might pull out, there have been (at least) two fruitful threads on puppet-dev on this topic: from Jan 2014, lots of discussion: https://groups.google.com/forum/#!msg/puppet-dev/4y9ZvbbkKBs/rmbhUlDvu9AJ from Oct 2014, less discussion but a crisp proposal: https://groups.google.com/forum/#!msg/puppet-dev/ENl4YndsuDE/PKwhqwpckyYJ 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-4380) Split non-core puppet functionality into modules
Title: Message Title Justin Stoller commented on PUP-4380 Re: Split non-core puppet functionality into modules Does this have implications for for supported modules and module pipelines (eg tagmail)? 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-4380) Split non-core puppet functionality into modules
Title: Message Title Eric Sorenson created an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Issue Type: Bug Assignee: Unassigned Created: 2015/04/06 5:13 PM Priority: Normal Reporter: Eric Sorenson To reduce the surface area of puppet itself and increase maintainability of non-core puppet, things which can be split out from it should be. Prime examples include the Nagios types (Redmine #4146 / PUP-1077) and some of the more esoteric single-OS types/providers like solaris zpools. These could still be combined at packaging time but the puppet repository itself would not contain them. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4380) Split non-core puppet functionality into modules
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-4380 Split non-core puppet functionality into modules Change By: Eric Sorenson Business Value: 452 Epic Name: Movenon-coreT/Ptomodules Epic Status: ToDo Workflow: ScrumTeam EngineeringEpic Workflow Issue Type: Bug Epic 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
