Jira (PUP-1515) types/providers should be loaded from specified environment
Title: Message Title
Nicholas Fagerlund updated an issue
Puppet / PUP-1515
types/providers should be loaded from specified environment
Change By:
Nicholas Fagerlund
When compiling a catalog, types and providers are validated, but while Puppet will load types from the agent -requested 's environment (modulo , it only loads providers from the compiling master's default environment (production) during one phase of the compilation . We should ensure we autoload types and providers from This is a problem because the same environment method that creates the {{provider}} parameter is specified sometimes called due to code in the *provider,* not the type . one example: If you have a custom resource type /provider only exists in another a non-default environment , and you declare a resource that is broken specifies a value for the {{provider}} attribute , it should not produce this can cause an {{invalid parameter provider}} error in another .The expected behavior is that Puppet will autoload types and providers from the agent's environment. original description:In Puppet 3 I am getting an error on all definitions for custom types. It says "Error 400 on SERVER: Invalid parameter provider...". Provider should be a given parameter for custom types because otherwise there is no way to specify which provider should be used with it. This is potentially a very major bug. Please let me know how I can help so you're able to reproduce and fix the issue. Final resolution: When validating resources during catalog compilation, Puppet will load types and providers from the environment that the catalog is being compiled for. (Modulo that other bug that causes cross-environment contamination.)
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-1515) types/providers should be loaded from specified environment
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-1515 types/providers should be loaded from specified environment Change By: Nicholas Fagerlund The autoloader currently loads When compiling a catalog, types and providers are validated, but while Puppet will load types from the agent-requested environment (modulo only loads providers from the default environment (production) during one phase of the compilation. We should ensure we autoload types and providers from the same environment that is specified.one example:If you have a custom type/provider in another environment that is broken, it should not produce an error in another environment. original description:In Puppet 3 I am getting an error on all definitions for custom types. It says "Error 400 on SERVER: Invalid parameter provider...". Provider should be a given parameter for custom types because otherwise there is no way to specify which provider should be used with it. This is potentially a very major bug. Please let me know how I can help so you're able to reproduce and fix the issue. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1515) types/providers should be loaded from specified environment
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1515 types/providers should be loaded from specified environment Change By: Eric Thompson If you have a custom type/provider in another environment that is broken, it should not produce an error in another environment. The autoloader currently loads types and providers from the default environment (production) during one phase of the compilation.We should ensure we autoload types and providers from the same environment that is specified. one example: If you have a custom type/provider in another environment that is broken, it should not produce an error in another environment. original description:In Puppet 3 I am getting an error on all definitions for custom types. It says "Error 400 on SERVER: Invalid parameter provider...". Provider should be a given parameter for custom types because otherwise there is no way to specify which provider should be used with it. This is potentially a very major bug. Please let me know how I can help so you're able to reproduce and fix the issue. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1515) types/providers should be loaded from specified environment
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1515 types/providers should be loaded from specified environment Change By: Eric Thompson If you have a custom type/provider in another environment that is broken, it should not produce an error in another environment. The autoloader currently loads types and providers from the default environment (production) during one phase of the compilation.We should ensure we autoload types and providers from the same environment that is specified.original description: In Puppet 3 I am getting an error on all definitions for custom types. It says "Error 400 on SERVER: Invalid parameter provider...". Provider should be a given parameter for custom types because otherwise there is no way to specify which provider should be used with it. This is potentially a very major bug. Please let me know how I can help so you're able to reproduce and fix the issue. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1515) types/providers should be loaded from specified environment
Title: Message Title Eric Thompson assigned an issue to Nicholas Fagerlund Puppet / PUP-1515 types/providers should be loaded from specified environment Change By: Eric Thompson Assignee: Nicholas Fagerlund Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-1515) types/providers should be loaded from specified environment
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1515 types/providers should be loaded from specified environment Change By: Eric Thompson Summary: Invalid parameter provider for custom types/providers should be loaded from specified environment Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
