Jira (PUP-5708) Deprecate pluginsync setting
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5708 Deprecate pluginsync setting Change By: Josh Cooper Release Notes Summary: The pluginsync setting is deprecated. By default, puppet will automatically do a pluginsync when requesting a new catalog, and will not pluginsync when applying a cached catalog. If pluginsync is specified explicitly on the command line or puppet.conf, then puppet will continue to observe the value of the setting. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5708) Deprecate pluginsync setting
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5708 Deprecate pluginsync setting Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5708) Deprecate pluginsync setting
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5708 Deprecate pluginsync setting Change By: Eric Thompson QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5708) Deprecate pluginsync setting
Title: Message Title William Hopper updated an issue Puppet / PUP-5708 Deprecate pluginsync setting Change By: William Hopper Scope Change Category: Adopted Scope Change Reason: Brought in to help parallelize direct puppet work, as other tickets were in progress Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5708) Deprecate pluginsync setting
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5708 Deprecate pluginsync setting Change By: Steve Barlow Sprint: Client 2016-01-27 , Client 2016-02-10 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5708) Deprecate pluginsync setting
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-5708 Deprecate pluginsync setting Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5708) Deprecate pluginsync setting
Title: Message Title Josh Cooper commented on PUP-5708 Re: Deprecate pluginsync setting I'm seeing a deprecation warning without specifying the pluginsync option on the command line or puppet.conf: $ bundle exec puppet agent --configprint pluginsync true $ bundle exec puppet agent --configprint config /Users/josh/.puppetlabs/etc/puppet/puppet.conf $ cat $(bundle exec puppet agent --configprint config) cat: /Users/josh/.puppetlabs/etc/puppet/puppet.conf: No such file or directory I wouldn't expect to see the deprecation warning unless it was explicitly specified on the command line or puppet.conf. Add Comment
Jira (PUP-5708) Deprecate pluginsync setting
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-5708
Deprecate pluginsync setting
Change By:
Josh Cooper
The {{pluginsync}} setting should be deprecated and instead a warning issued if the behavior of pluginsyncing or not should be based setting is specified explicitly on whether we are applying a cached catalog the command line or not puppet . Otherwise conf. In 5.x , the setting will be removed. The motivation is because catalog and plugins can be inconsistent . For example, with the following combinations:{noformat}pluginsync=falseuse_cached_catalog=false{noformat}Will cause the agent to get the latest catalog may contain a , but use older plugins. The new catalog may reference property /parameters that the older pluginsync old plugins don ' ed type ( t know how to manage, or the agent may not have any plugins. Worse, the agent run may succeed, but due to semantic differences between the catalog and plugins, not achieve the desired state.OR { noformat}pluginsync=trueuse_cached_catalog=true { lib/puppet/type/foo.rb noformat } }) doesn't know about Will cause the agent to use an old catalog with the latest plugins . The new pluginsync may have removed support for managing property/parameters contained in the catalog.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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
Jira (PUP-5708) Deprecate pluginsync setting
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-5708 Deprecate pluginsync setting Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5708) Deprecate pluginsync setting
Title: Message Title William Hopper updated an issue Puppet / PUP-5708 Deprecate pluginsync setting Change By: William Hopper Sprint: Client 2016- 02 01 - 10 27 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5708) Deprecate pluginsync setting
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5708 Deprecate pluginsync setting Change By: Josh Cooper Sprint: Client 2016-02- 24 (Burn FF) 10 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5708) Deprecate pluginsync setting
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-5708
Deprecate pluginsync setting
Change By:
Josh Cooper
The {{pluginsync}} setting should be deprecated and instead the behavior of pluginsyncing or not should be based on whether we are applying a cached catalog or not. Otherwise, the catalog and plugins can be consistent inconsistent . For example, the catalog may contain a new property that the older pluginsync'ed type ({{lib/puppet/type/foo.rb}}) doesn't know about.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-5708) Deprecate pluginsync setting
Title: Message Title Josh Cooper created an issue Puppet / PUP-5708 Deprecate pluginsync setting Issue Type: Task Assignee: Unassigned Created: 2016/01/14 8:38 AM Priority: Normal Reporter: Josh Cooper The pluginsync setting should be deprecated and instead the behavior of pluginsyncing or not should be based on whether we are applying a cached catalog or not. Otherwise, the catalog and plugins can be consistent. For example, the catalog may contain a new property that the older pluginsync'ed type (lib/puppet/type/foo.rb) doesn't know about. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5708) Deprecate pluginsync setting
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5708 Deprecate pluginsync setting Change By: Josh Cooper Sprint: Client 2016-02-24 (Burn FF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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.
