Jira (PUP-4669) Varargs support for (defined) types (and possibly classes)
Title: Message Title Henrik Lindberg commented on PUP-4669 Re: Varargs support for (defined) types (and possibly classes) We have the syntax already, but it is forbidden to use "varargs" (a.k.a "captures rest") for defines and classes (validation flags it as an error). 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-5912) Implement a human friendly PCore serialization format
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5912 Implement a human friendly PCore serialization format Change By: Henrik Lindberg Issue Type: Task New Feature 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-5912) Implement a human friendly PCore serialization format
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-5912 Implement a human friendly PCore serialization format Issue Type: Task Assignee: Unassigned Created: 2016/02/16 6:21 PM Priority: Normal Reporter: Henrik Lindberg The serializers in PUP-5908 and PUP-5909 focus on machine to machine communication. They will contain many optimizations and tricks to make those formats as efficient as possible for the underlying encoding. They will look like complete gibberish to a human. In order to make models humanly readable (although not exclusively targeting humans) we should implement a serializer that has verbose output. This format may also be used for someone that is writing utility tools in a language/environment where the investment to support the Machine to Machine formats is prohibiting. (There are many tasks you can perform with something like json-query on such a format; defining the json query that can make sense out of the highly optimized and tabulated machine to machine formats is almost impossible). We should use JSON for this. When we have this format, it is easy to transform between them. A file with a MM format can be deserialized and re-serialized possibly even without having to create a representation. This enables writing a tool for inspection of binary serialization and other similar use cases.
Jira (PUP-1829) Define PCore - the Puppet Meta Meta Model
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1829 Define PCore - the Puppet Meta Meta Model Change By: Henrik Lindberg The PCore model is the puppet meta meta model which will be used to describe all puppet meta models.If your head is spinning:* A meta model is like a schema e.g. the json-schema for a puppet catalog* A meta meta model is like the jsonschema json-schema, that defines what you can define in a json-schemaIn Puppet we now have a very rich Type System. PCore takes advantage of that and this allows us to define very compact models.The first model that we express is the PCore meta meta model as it defines what follows. The first real model we aim to express using PCore is the AST model.We are doing this because existing modeling Ecore, jsonschema, yaml-schema, etc. are based on assumptions about the target language (java, json, yaml) and thus contain features suitable for each of those technologies (and naturally also lacking features). While it is possible to model anything with those, it requires yet another abstraction layer since the basic types available are not enough to describe the puppet types. With our own model we require fewer abstraction layers. What we process is already typed by the type system, and it should be just as easy to describe a model as it is to define a value's type. When something is typed by the type system, enough information is known to enable that the value is serialized. This means that objects do not have to support a variety of serialization protocols (to_yaml, to_json, to_msgpack, to_this, to_that). To work around that, in Puppet the protocol is now "to_data_hash" and "from_data_hash" and that step reduces the information to a hash of serializable values and that is in turned serialized with a to_yaml etc. When doing this we created another problem for us; this is a lossy transformation ! (This is one reason it is hard to serialize anything but the most rudimentary data types9).The work consists of:* Specifying PCore* Implementing PCore in PCore* Specifying how an instance model (a catalog, an AST, etc) + a PCore model is used to serialize and deserialize that model,* It is expected that this work will spin off requirements for enhancements to the type system (Some already identified and worked on).Other tickets will contain the more concrete things (like writing a serializer) PCore is an enabler for many future features:* partitioning results to make what is required in each communication to be smaller* efficient sending of a machine state (the RAL) as a fact* a more efficient replacement for plugin-sync * describing resource types in puppet* polyglot implementations (native resource types)* functions on the agent (without distributing the pp source to all agents)* and many moreThis ticket is about none of the future things - only the basic processing needed to support the "Native Puppet Parser" but with the required concepts in place for higher order functionality (or at least that the implementation does not block the higher order functionality by being so simplistic that it has to be immediately redone).The design has to be as future proof as we can reasonably make it. As this sits at the core it is both hard and takes a long time to change when done wrong. We should rather err
Jira (PUP-5906) Native Puppet Parser - make puppet use native parse and validate
Title: Message Title Henrik Lindberg commented on PUP-5906 Re: Native Puppet Parser - make puppet use native parse and validate The current state of this work is that we are exploring designs and definitions as well as prototyping. 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-5910) Define the PCore model for Parser Related models; e.g AST
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5910 Define the PCore model for Parser Related models; e.g AST Change By: Henrik Lindberg Summary: Define the PCore model for Parser Related models ; e.g AST 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-5911) Define the content of an .xpp file
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-5911 Define the content of an .xpp file Issue Type: Task Assignee: Unassigned Created: 2016/02/16 5:58 PM Priority: Normal Reporter: Henrik Lindberg We need to specify the content of an .xpp file - it will naturally contain the serialized AST, but since the action of writing it, and reading it is asynchronous it is important that the encoding used in the .xpp can be learned by inspecting it. The idea is that the parser checks if there is an .xpp file and if it is newer that the corresponding .pp file. If so it will use the .xpp. There could potentially be a very long time between the .xpp is created and the time it is being used (several years). We may have made advancements even if the technology used to serialize is still based on the same technology (say MsgPack) we benefit from knowing up front about the version. We may also in the future use a different encoding; a better technology than MsgPack say) we do not want to change the extension for that. We may also want to conduct experiments with different formats, benchmarking etc. Having the parser check for more than one name/extension make it a lot more expensive. Hence - the .xpp file must have some kind of envelope that all .xpp files have. It must be something simple like a first line in ascii containing a protocol URI that defines the format (i.e. the content of the envelope is described in the content that URI identifies. This is also how we at runtime can map the content to a deserializer.
Jira (PUP-5910) Define the PCore model for Parser Related models
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-5910 Define the PCore model for Parser Related models Issue Type: New Feature Assignee: Unassigned Created: 2016/02/16 5:49 PM Priority: Normal Reporter: Henrik Lindberg In order to serialize/deserialize everything that is in a resulting AST there needs to be a model that describes all the AST things: The AST nodes themselves The Locator containing source code and source line offsets (not sure if there are any additional references to runtime objects that are not already modelled in Ecore/RGen). Add Comment
Jira (PUP-5909) Implement a PCore serializer for JSON Machine to Machine
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-5909 Implement a PCore serializer for JSON Machine to Machine Issue Type: New Feature Assignee: Unassigned Created: 2016/02/16 5:45 PM Priority: Normal Reporter: Henrik Lindberg This format should be as close as possible to the MsgPack PCore serializer format. This format is useful long term for efficient serialization to environments where MsgPack may not be suitable (_javascript_). Short term this is of value to be able to debug and test serialization concepts like tabulation more easily than on MsgPack. The output of this serializer is not intended to be human friendly. Its main goal is to be as efficient as possible when two parties need to communicate using JSON. Add Comment
Jira (PUP-5907) Define the PCore Serialization API and Features
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5907 Define the PCore Serialization API and Features Change By: Henrik Lindberg Scrum Team: Language 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-5908) Implement a PCore MsgPack Serializer
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5908 Implement a PCore MsgPack Serializer Change By: Henrik Lindberg Scrum Team: Language 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-5908) Implement a PCore MsgPack Serializer
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-5908 Implement a PCore MsgPack Serializer Issue Type: New Feature Assignee: Unassigned Created: 2016/02/16 5:41 PM Priority: Normal Reporter: Henrik Lindberg 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
Jira (PUP-5907) Define the PCore Serialization API and Features
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-5907 Define the PCore Serialization API and Features Issue Type: Task Assignee: Unassigned Created: 2016/02/16 5:40 PM Priority: Normal Reporter: Henrik Lindberg 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://gr
Jira (PUP-4669) Varargs support for (defined) types (and possibly classes)
Title: Message Title Eric Sorenson commented on PUP-4669 Re: Varargs support for (defined) types (and possibly classes) For the record, this ticket was the subject of a very detailed and exciting discussion at Gent contributor summit. I think most of the pro/con arguments from the room are captured in the comments. IMO this is interesting but a pretty small niche and I would be pretty cautious about putting more special syntax in to support it. 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-5900) Global noop true should override resource noop=>false
Title: Message Title Ryan Whitehurst commented on PUP-5900 Re: Global noop true should override resource noop=>false Eric Sorenson That actually gets into one of the fundamental problems with the noop flag IMO. The noop flag actually means "set the default value for the noop parameter to true before applying the catalog during this run", and yes, that means that individual resource parameters should win. However, IMO, you shouldn't be manipulating the catalog directly from the agent at all. The only thing you should be able to modify is the application of the catalog as a whole, in which case the options would be "apply the catalog normally" or "simulate each resource and tell me what would change without actually changing them". That's not what the noop parameter means, but in my experience, it seems that's what many people actually want from it. 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-5906) Native Puppet Parser - make puppet use native parse and validate
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5906 Native Puppet Parser - make puppet use native parse and validate Change By: Henrik Lindberg Scrum Team/s: Language 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-5906) Native Puppet Parser - make puppet use native parse and validate
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-5906 Native Puppet Parser - make puppet use native parse and validate Issue Type: Epic Assignee: Unassigned Created: 2016/02/16 5:02 PM Fix Versions: PUP 4.x Priority: Normal Reporter: Henrik Lindberg This epic is for work that aims at making it possible for the Ruby Puppet Runtime to benefit from a native (C++) implementation of lexer/parser/validator by getting increased performance and throughout in every compilation. This is the starting point for many features to come and we have to constrain what we are implementing to get early feedback and fix the smaller problems before they get to big. The simple principle that this is built on is that: If there is a fast loading .xpp file that contains already parsed and validated AST then the parser can use that instead of performing the chain of lexing/parsing/building-AST/validating before it can start evaluating the AST. From a user perspective this should be completely transparent. (Except naturally opting in/out when this feature is new and experimental). As said earlier, this is the starting point enabling many interesting use cases: pre parsing everything in a module
Jira (PUP-5900) Global noop true should override resource noop=>false
Title: Message Title Eric Sorenson commented on PUP-5900 Re: Global noop true should override resource noop=>false Even realizing all the changes --noop still makes, this one is counterintuitive because it violates the common paradigm of "specific beats general". A flag set on a manual CLI execution should always beat everything else. This just shows the fallacy of thinking anything in computers is really "intuitive". I agree with the principle of "specific beats general" but the interpretation in #20679 was inverted from your comment: "specific" meant noop specified on a particular resource and "general" meant noop on the global command line. 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-1829) Define PCore - the Puppet Meta Meta Model
Title: Message Title Henrik Lindberg commented on PUP-1829 Re: Define PCore - the Puppet Meta Meta Model Thomas Hallgren Assigned this to you to review the ticket itself; does it contain enough scope and detail. (Serialization will be dealt with separately). 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-1829) Define PCore - the Puppet Meta Meta Model
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1829 Define PCore - the Puppet Meta Meta Model Change By: Henrik Lindberg Story Points: 24 5 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-1829) Define PCore - the Puppet Meta Meta Model
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-1829 Define PCore - the Puppet Meta Meta Model Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren 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-1829) Define PCore - the Puppet Meta Meta Model
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1829 Define PCore - the Puppet Meta Meta Model Change By: Henrik Lindberg The PCore model is the puppet meta meta model which will be used to describe all puppet meta models.If your head is spinning:* A meta model is like a schema e.g. the json-schema for a puppet catalog* A meta meta model is like the jsonschema json-schema, that defines what you can define in a json-schemaIn Puppet we now have a very rich Type System. PCore takes advantage of that and this allows us to define very compact models.The first model that we express is the PCore meta meta model as it defines what follows. The first real model we aim to express using PCore is the AST model.We are doing this because existing modeling Ecore, jsonschema, yaml-schema, etc. are based on assumptions about the target language (java, json, yaml) and thus contain features suitable for each of those technologies (and naturally also lacking features). While it is possible to model anything with those, it requires yet another abstraction layer since the basic types available are not enough to describe the puppet types. With our own model we require fewer abstraction layers. What we process is already typed by the type system, and it should be just as easy to describe a model as it is to define a value's type. When something is typed by the type system, enough information is known to enable that the value is serialized. This means that objects do not have to support a variety of serialization protocols (to_yaml, to_json, to_msgpack, to_this, to_that). To work around that, in Puppet the protocol is now "to_data_hash" and "from_data_hash" and that step reduces the information to a hash of serializable values and that is in turned serialized with a to_yaml etc. When doing this we created another problem for us; this is a lossy transformation ! (This is one reason it is hard to serialize anything but the most rudimentary data types9).The work consists of:* Specifying PCore* Implementing PCore in PCore* Specifying how an instance model (a catalog, an AST, etc) + a PCore model is used to serialize and deserialize that model, * It is expected that this work will spin off requirements for enhancements to the type system (Some already identified and worked on). Other tickets will contain the more concrete things (like writing a serializer) Add Comment
Jira (PUP-1829) Define PCore - the Puppet Meta Meta Model
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1829 Define PCore - the Puppet Meta Meta Model Change By: Henrik Lindberg The PCore model is the puppet meta meta model which is will be used to describe all puppet meta models.If your head is spinning:* A meta model is like a schema e.g. the types in the json-schema for a puppet system catalog* A meta meta model is like the jsonschema json-schema, that defines what you can define in a json-schemaIn Puppet we now have a very rich Type System . It plays PCore takes advantage of that and this allows us to define very compact models.The first model that we express is the same role PCore meta meta model as ECore it defines what follows . This The first real model we aim to express using PCore is required the AST model.We are doing this because existing modeling Ecore, jsonschema, yaml-schema, etc. are based on assumptions about the Puppet target language (java, json, yaml) and thus contain features suitable for each of those technologies (and naturally also lacking features). While it is possible to model anything with those, it requires yet another abstraction layer since the basic types available are not (easily) directly describable in ECore enough to describe the puppet types . Currently With our own model we have, require fewer abstraction layers. What we process is already typed by the Puppet::Pops::Types Ecore model type system , and this model it should be expanded just as easy to describe a model as it is to define a value's type. When something is typed by the type system , enough information is known to enable that the value is serialized. This means that objects do not have to support a variety of serialization protocols (to_yaml, to_json, to_msgpack, to_this, to_that). To work around that, in Puppet the protocol is now "to_data_hash" and renamed "from_data_hash" and that step reduces the information to PCore a hash of serializable values and that is in turned serialized with a to_yaml etc . When doing this we created another problem for us; this is a lossy transformation ! (This is one reason it is hard to serialize anything but the most rudimentary data types9). The work consists of: * implementing the Specifying PCore metamodel * implementing a validator Implementing PCore in PCore * * writing issues Specifying how an instance model ( i.e. formal error messages)* implementing a tree dumper (textual representation catalog, an AST, etc ) * implementing factory / helper methods* PCore to Ecore generator to Ruby (to realize the classes into running code)* "scraping" 3.x types (and maybe? providers) to form + a new model of "old" implementations PCore model is used by the Evaluator to serialize and the new Loaders. deserialize that model, The functionality is experimental in 3.6. and is expected to be released in 4.0. Other tickets will contain the more concrete things (like writing a serializer)
Jira (PUP-1829) Define PCore - the Puppet Meta Meta Model
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1829 Define PCore - the Puppet Meta Meta Model Change By: Henrik Lindberg Summary: Implement a Define PCore - the Puppet Core Meta Meta Model (PCore) 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-5878) acceptance: agent can reconnect after master failure
Title: Message Title Michael Smith assigned an issue to Eric Thompson Puppet / PUP-5878 acceptance: agent can reconnect after master failure Change By: Michael Smith Assignee: Eric Thompson 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-1795) Issue warning for numeric coercion
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1795 Issue warning for numeric coercion Change By: Henrik Lindberg Reporter: Andrew Parker Henrik Lindberg 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-1795) Issue warning for numeric coercion
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-1795 Issue warning for numeric coercion Change By: Henrik Lindberg Assignee: Andrew Parker 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-1829) Implement a Puppet Core Meta Model (PCore)
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-1829 Implement a Puppet Core Meta Model (PCore) Change By: Henrik Lindberg Assignee: Andrew Parker Henrik Lindberg 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 (PDB-2434) PDB status missing in PE
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2434 PDB status missing in PE Change By: Wyatt Alt Scope Change Category: Found Scope Change Reason: status bug found by 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 (PDB-2434) PDB status missing in PE
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2434 PDB status missing in PE Change By: Wyatt Alt Sprint: PuppetDB 2016-02-24 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 (PDB-2434) PDB status missing in PE
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2434 PDB status missing in PE Change By: Wyatt Alt Story Points: 1 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 (PDB-2434) PDB status missing in PE
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2434 PDB status missing in PE Issue Type: Bug Affects Versions: PDB 4.0.0 Assignee: Wyatt Alt Created: 2016/02/16 2:35 PM Priority: Normal Reporter: Wyatt Alt 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 unsubscr
Jira (PDB-2269) Store cached catalog reason
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2269 Store cached catalog reason Change By: Kenneth Barber Flagged: Impediment 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-5898) Data types seems to be messed up on hash parameters
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5898 Data types seems to be messed up on hash parameters Change By: Henrik Lindberg Fix Version/s: PUP 4.3.3 Fix Version/s: PUP 3.8.7 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-5815) Add a puppet agent command line option to fail the run if the catalog's environment doesn't match
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-5815 Add a puppet agent command line option to fail the run if the catalog's environment doesn't match 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 (PDB-2269) Store cached catalog reason
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2269 Store cached catalog reason Change By: Kenneth Barber Flagged: Impediment 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-4929) Acceptance test for packages has dependency on rubygems.org
Title: Message Title Michael Smith updated an issue Puppet / PUP-4929 Acceptance test for packages has dependency on rubygems.org Change By: Michael Smith Scope Change Category: Found Scope Change Reason: Became transient in puppet-server pipelines 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-4929) Acceptance test for packages has dependency on rubygems.org
Title: Message Title Michael Smith updated an issue Puppet / PUP-4929 Acceptance test for packages has dependency on rubygems.org Change By: Michael Smith Sprint: Client 2015-09-02 , 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.
Jira (PUP-4929) Acceptance test for packages has dependency on rubygems.org
Title: Message Title Michael Smith commented on PUP-4929 Re: Acceptance test for packages has dependency on rubygems.org Impacting puppet-server pipelines. 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-4929) Acceptance test for packages has dependency on rubygems.org
Title: Message Title Michael Smith updated an issue Puppet / PUP-4929 Acceptance test for packages has dependency on rubygems.org Change By: Michael Smith Release Notes: Not Needed 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-5905) transient test failures in common_package_name_in_different_providers.rb test
Title: Message Title Christopher Price commented on PUP-5905 Re: transient test failures in common_package_name_in_different_providers.rb test It looks like these are failing due to a connection error w/rubygems.org. Michael Smith pointed me to PUP-4929 , which was closed as "cannot repro". Michael Smith do you have any thoughts on what to do for now? I can just re-run these jobs and ignore the issue if it doesn't continue to come up, or I can re-open PUP-4929 , or we can use this ticket as a replacement for PUP-4929 ... any thoughts? 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-5905) transient test failures in common_package_name_in_different_providers.rb test
Title: Message Title
Christopher Price updated an issue
Puppet / PUP-5905
transient test failures in common_package_name_in_different_providers.rb test
Change By:
Christopher Price
We have recently experienced what appear to be transient failures in the acceptance test {{common_package_name_in_different_providers.rb}}. These seem to come up occasionally, usually (perhaps always) on redhat systems, but not usually on more than one or two cells in a given run. We're seeing these on both our {{stable}} and {{master}} branches.Not yet sure where this ticket should go; for now I'm trying to tease out whether or not other teams have seen these before, or whether there's an SME on this. If it appears to be specific to Puppet Server then we can move this ticket to SERVER and dig in further.A few recent failures:https://jenkins.puppetlabs.com/view/puppet-server/view/all/job/platform_puppet-server_integration-system_no-conditional_full-master/LAYOUT=redhat7-64ma-64a,LDAP_TYPE=default,PLATFORM=default,label=beaker/114/consoleFull https://jenkins.puppetlabs.com/job/platform_puppet-server_integration-system_no-conditional_full-stable/77/
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,
Jira (PUP-5897) Support Ubuntu 16.04 in systemd provider
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5897 Support Ubuntu 16.04 in systemd provider Change By: Kylo Ginsberg Scope Change Reason: Trivial, low-risk community contribution. 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-5905) transient test failures in common_package_name_in_different_providers.rb test
Title: Message Title Christopher Price commented on PUP-5905 Re: transient test failures in common_package_name_in_different_providers.rb test ping Michael Smith for visibility since he appears to know at least some things about this test 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-5905) transient test failures in common_package_name_in_different_providers.rb test
Title: Message Title
Christopher Price updated an issue
Puppet / PUP-5905
transient test failures in common_package_name_in_different_providers.rb test
Change By:
Christopher Price
We have recently experienced what appear to be transient failures in the acceptance test {{common_package_name_in_different_providers.rb}}. These seem to come up occasionally, usually (perhaps always) on redhat systems, but not usually on more than one or two cells in a given run. We're seeing these on both our {{stable}} and {{master}} branches.Not yet sure where this ticket should go; for now I'm trying to tease out whether or not other teams have seen these before, or whether there's an SME on this. If it appears to be specific to Puppet Server then we can move this ticket to SERVER and dig in further.A few recent failures: https://jenkins.puppetlabs.com/view/puppet-server/view/all/job/platform_puppet-server_integration-system_no-conditional_full-master/LAYOUT=redhat7-64ma-64a,LDAP_TYPE=default,PLATFORM=default,label=beaker/114/consoleFull
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-5905) transient test failures in common_package_name_in_different_providers.rb test
Title: Message Title
Christopher Price updated an issue
Puppet / PUP-5905
transient test failures in common_package_name_in_different_providers.rb test
Change By:
Christopher Price
We have recently experienced what appear to be transient failures in the acceptance test {{common_package_name_in_different_providers.rb}}. These seem to come up occasionally, usually (perhaps always) on redhat systems, but not usually on more than one or two cells in a given run. We're seeing these on both our {{stable}} and {{master}} branches.Not yet sure where this ticket should go; for now I'm trying to tease out whether or not other teams have seen these before, or whether there's an SME on this. If it appears to be specific to Puppet Server then we can move this ticket to SERVER and dig in further. A few recent failures:
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-5897) Support Ubuntu 16.04 in systemd provider
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5897 Support Ubuntu 16.04 in systemd provider Change By: Kylo Ginsberg Scope Change Category: Adopted 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-5905) transient test failures in common_package_name_in_different_providers.rb test
Title: Message Title Christopher Price created an issue Puppet / PUP-5905 transient test failures in common_package_name_in_different_providers.rb test Issue Type: Bug Assignee: Unassigned Created: 2016/02/16 11:55 AM Priority: Normal Reporter: Christopher Price We have recently experienced what appear to be transient failures in the acceptance test common_package_name_in_different_providers.rb. These seem to come up occasionally, usually (perhaps always) on redhat systems, but not usually on more than one or two cells in a given run. We're seeing these on both our stable and master branches. Not yet sure where this ticket should go; for now I'm trying to tease out whether or not other teams have seen these before, or whether there's an SME on this. If it appears to be specific to Puppet Server then we can move this ticket to SERVER and dig in further. Add Comment
Jira (PUP-5897) Support Ubuntu 16.04 in systemd provider
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5897 Support Ubuntu 16.04 in systemd provider Change By: Kylo Ginsberg Release Notes Summary: This fix specifies systemd as the default service provider for Ubuntu 16.04. (But note that this release of puppet-agent does not yet include packages for 16.04.) 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-5897) Support Ubuntu 16.04 in systemd provider
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5897 Support Ubuntu 16.04 in systemd provider Change By: Kylo Ginsberg 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-5897) Support Ubuntu 16.04 in systemd provider
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-5897 Support Ubuntu 16.04 in systemd provider Change By: Michael Smith Status: Ready for CI Test Assignee: Kylo Ginsberg 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-5734) Value of the key dependencies in the metadata.json of modules isn't checked
Title: Message Title Anderson Mills commented on PUP-5734 Re: Value of the key dependencies in the metadata.json of modules isn't checked Waiting on a fixup for the test case, then happy to merge. 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-5701) Compare files using checksum_value
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-5701 Compare files using checksum_value Change By: Michael Smith Status: Ready for CI Test Assignee: Josh Cooper 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 (PDB-2126) Add the `catalog_uuid` and 'code_id' to catalogs and `reports`
Title: Message Title Kenneth Barber commented on PDB-2126 Re: Add the `catalog_uuid` and 'code_id' to catalogs and `reports` First PR on the service merged, now need to review/merge the pe-puppetdb change: https://github.com/puppetlabs/pe-puppetdb-extensions/pull/161 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-5802) Yum provider incorrectly computes epoch for RPM package versions
Title: Message Title Michael Smith updated an issue Puppet / PUP-5802 Yum provider incorrectly computes epoch for RPM package versions Change By: Michael Smith Sprint: Client Community Triage 2016-03-09 (Burn CF) 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-5526) (Static Catalog) As a puppet administrator, I want the catalog that I apply to produce the same results regardless of the updates that happen to out-of-band file content.
Title: Message Title Erik Dasher commented on PUP-5526 Re: (Static Catalog) As a puppet administrator, I want the catalog that I apply to produce the same results regardless of the updates that happen to out-of-band file content. I believe I can work around PUP-5860; I intend to curl the appropriate endpoints and validate their output (a catalog) rather than making an end to end test that uses the agent (unless PUP-5860 becomes unblocked in the very near future.) 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-5533) (Static Catalog) As a puppet administrator, I should be able to correlate all agent run reports to a catalog.
Title: Message Title Erik Dasher commented on PUP-5533 Re: (Static Catalog) As a puppet administrator, I should be able to correlate all agent run reports to a catalog. This is Blocked on PDB-2126. 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-5533) (Static Catalog) As a puppet administrator, I should be able to correlate all agent run reports to a catalog.
Title: Message Title Erik Dasher commented on PUP-5533 Re: (Static Catalog) As a puppet administrator, I should be able to correlate all agent run reports to a catalog. Kenn Hussey John Duarte Sean Griffin My understanding is that this feature is not ready to test until PDB-2126 is in a build. 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-5535) (Static Catalog) As a puppet administrator I want to reduce the load on my compiler masters when reapplying a cached catalog
Title: Message Title Erik Dasher commented on PUP-5535 Re: (Static Catalog) As a puppet administrator I want to reduce the load on my compiler masters when reapplying a cached catalog I intend to touch test this late in the Burnside cycle by creating a situation where an agent has a cached catalog, the agent is running 'puppet agent -t' in a loop, and I'm watching the output of top and the puppetserver log on the server. 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-5535) (Static Catalog) As a puppet administrator I want to reduce the load on my compiler masters when reapplying a cached catalog
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5535 (Static Catalog) As a puppet administrator I want to reduce the load on my compiler masters when reapplying a cached catalog Change By: Erik Dasher Priority: Normal Minor 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-5900) Global noop true should override resource noop=>false
Title: Message Title Kylo Ginsberg commented on PUP-5900 Re: Global noop true should override resource noop=>false No worries Daniel Parks; Jira makes it pretty easy to fat-finger assignment/etc so I get that all the time and never interpret it weirdly Also, I agree with Henrik: if something is of public interest (which I'd think almost always applies to the PUP project), I'd prefer it open. The only natural exceptions are: security issues of course, but those should start with an email to security@ maybe if there's sensitive data, but even there I'd rather it were sanitized first (unless that's arduous for some reason) 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-5880) Support optional dependencies in Metadata.json
Title: Message Title Henrik Lindberg commented on PUP-5880 Re: Support optional dependencies in Metadata.json If we decide to move forward on this we need a cross team epic so we can correlate the work that is needed. 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-5880) Support optional dependencies in Metadata.json
Title: Message Title
Henrik Lindberg commented on PUP-5880
Re: Support optional dependencies in Metadata.json
This is also very much a Language team concern since dependencies are used to control the visibility between modules in 4.x. Adding optional dependencies requires additional handling in the runtime.
I am very much +1 on the feature in general.
But, isn't the issue here that it is not possible to specify a conditional dependency? I.e. "on platform P this module depends on Y". If a module truly does not use the features of another module, then it should not be a dependency. There is however the need to also support "bundles/feature/configuration" modules that more or less just consists of dependencies ("use these together"). The distinction will become more and more important as the dependencies will increase in importance.
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-5898) Data types seems to be messed up on hash parameters
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5898 Data types seems to be messed up on hash parameters Change By: Henrik Lindberg Assignee: Thomas Hallgren 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-5900) Global noop true should override resource noop=>false
Title: Message Title Daniel Parks commented on PUP-5900 Re: Global noop true should override resource noop=>false Oops. Accidentally assigned this to you for a second, Kylo Ginsberg. I'm not just passively-aggressivly suggesting you work it RIGHT NOW. ;p 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-5836) Splat operator should turn Iterator into an array
Title: Message Title Thomas Hallgren commented on PUP-5836 Re: Splat operator should turn Iterator into an array Spec PR-66 merged to master at 2a95db5. 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-5900) Global noop true should override resource noop=>false
Title: Message Title Daniel Parks assigned an issue to Unassigned Puppet / PUP-5900 Global noop true should override resource noop=>false Change By: Daniel Parks Assignee: Kylo Ginsberg 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-5900) Global noop true should override resource noop=>false
Title: Message Title Daniel Parks assigned an issue to Kylo Ginsberg Puppet / PUP-5900 Global noop true should override resource noop=>false Change By: Daniel Parks Assignee: Kylo Ginsberg 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-5728) Change default parsing of manifest files to UTF-8
Title: Message Title
Ryan Gard commented on PUP-5728
Re: Change default parsing of manifest files to UTF-8
Functional Review
Verified as fixed with build 6522aa18d8338b9ffdc613ea7e750a633d4ec6d5.
Environment
Agent: Windows Server 2012 R2 (WIN_SUT)
Test Case 1 Reproduction Steps
Install Puppet Agent on WIN_SUT.
Create the ERB template "C:\template.erb" (UTF-8 Encoding) on the WIN_SUT with the following content:
尻屌屛屗尐少
<%= @text %>
漕滴滸漛漣
Create the manifest "C:\test.pp" (UTF-8 Encoding) on the WIN_SUT with the following content:
$text='ᅪᅫᅇᅽᄟ'
file { 'c:\漕滴滸漛漣':
ensure => file,
Jira (PUP-5900) Global noop true should override resource noop=>false
Title: Message Title Ryan Whitehurst commented on PUP-5900 Re: Global noop true should override resource noop=>false Even realizing all the changes --noop still makes, this one is counterintuitive because it violates the common paradigm of "specific beats general". A flag set on a manual CLI execution should always beat everything else. 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-5742) Add ability to create Aliases for Puppet Types in PL
Title: Message Title Thomas Hallgren commented on PUP-5742 Re: Add ability to create Aliases for Puppet Types in PL Spec merged to master at 95bd7c5. 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 (FACT-1340) Update Facter Acceptance tests for cisco-5
Title: Message Title Kenn Hussey commented on FACT-1340 Re: Update Facter Acceptance tests for cisco-5 The decision was to confine tests based on tags in the future, but we will merge these changes in the short term. 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-5804) Update Puppet Acceptance tests for cisco-5
Title: Message Title Kenn Hussey commented on PUP-5804 Re: Update Puppet Acceptance tests for cisco-5 The decision was to confine tests based on tags in the future, but we will merge these changes in the short term. 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-5735) Remove usage of win32-security gem
Title: Message Title Glenn Sarti commented on PUP-5735 Re: Remove usage of win32-security gem Modules depending on win32-security puppetlabs-acl https://github.com/puppetlabs/puppetlabs-acl/blob/master/lib/puppet/util/monkey_patches.rb https://github.com/puppetlabs/puppetlabs-acl/blob/master/lib/puppet/provider/acl/windows/base.rb reidmv-windows_package (looks like a copy of all the windows utils from Pup 2.7.x) This module may not be an issue as it's only applicable for Puppet less than 3.0, where as our changes are targetted at Pup 4.x https://forge.puppetlabs.com/reidmv/windows_package https://github.com/reidmv/puppet-module-windows_package/blob/master/lib/puppet/util/windows_package/user.rb 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-5728) Change default parsing of manifest files to UTF-8
Title: Message Title Ryan Gard commented on PUP-5728 Re: Change default parsing of manifest files to UTF-8 Functional Review Verified as fixed with build 6522aa18d8338b9ffdc613ea7e750a633d4ec6d5. Environment Agent: Windows Server 2012 R2 (WIN_SUT) Agent: CentOS 7 x64 (LINUX_SUT) Test Case 1 Reproduction Steps Install Puppet Agent on WIN_SUT. Create the EPP template "C:\template.epp" (UTF-8 Encoding) on the WIN_SUT with the following content: 尻屌屛屗尐少 <%= $text %> 漕滴滸漛漣 Install ConEmu. (This enables displaying Unicode content without changing codepage.) Open a ConEmu console session. Verify that codepage is 437: chcp
Jira (PUP-5728) Change default parsing of manifest files to UTF-8
Title: Message Title
Ryan Gard commented on PUP-5728
Re: Change default parsing of manifest files to UTF-8
Functional Review
Verified as fixed with build 6522aa18d8338b9ffdc613ea7e750a633d4ec6d5.
Environment
Agent: Windows Server 2012 R2 (WIN_SUT)
Test Case 1 Reproduction Steps
Install Puppet Agent on WIN_SUT.
Create the EPP template "C:\template.epp" (UTF-8 Encoding) on the WIN_SUT with the following content:
尻屌屛屗尐少
<%= $text %>
漕滴滸漛漣
Create the manifest "C:\test.pp" (UTF-8 Encoding) on the WIN_SUT with the following content:
$text='ᅪᅫᅇᅽᄟ'
file { 'c:\漕滴滸漛漣':
ensure => file,
Jira (PUP-5728) Change default parsing of manifest files to UTF-8
Title: Message Title
Ryan Gard commented on PUP-5728
Re: Change default parsing of manifest files to UTF-8
Functional Review
Verified as fixed with build 6522aa18d8338b9ffdc613ea7e750a633d4ec6d5.
Environment
Agent: Windows Server 2012 R2 (WIN_SUT)
Test Case 1 Reproduction Steps
Install Puppet Agent on WIN_SUT.
Create the manifest "C:\test.pp" (UTF-8 Encoding) on the WIN_SUT with the following content:
file { "c:\\unicode_\u5BF9\u5BFA\u5BFB\u5BFD\u5BFE\u5BFF\u5BF8":
ensure => file,
content => "\u5BF9\u5BFA\u5BFB\u5BFD\u5BFE\u5BFF\u5BF8",
}
file { 'c:\漕滴滸漛漣':
ensure => file,
content => '漕滴滸漛漣',
Jira (PDB-2433) Add deprecation warnings for old command versions
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2433 Add deprecation warnings for old command versions Change By: Kenneth Barber Affects Version/s: PDB 3.2.x We should deprecated need to put back the deprecation messages for old command versions in master and stable. This was removed when we retired the old commands, but we put them back and never reverted the deprecation warnings.Here is the old code that performed this:https://github.com/puppetlabs/puppetdb/blob/2.3.x/src/com/puppetlabs/puppetdb/command.clj#L323 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 (PDB-2433) Add deprecation warnings for old command versions
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2433 Add deprecation warnings for old command versions Change By: Andrew Roetker Sprint: PuppetDB 2016-03-09 Issue Type: Improvement Bug 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 (PDB-2433) Add deprecation warnings for old command versions
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2433 Add deprecation warnings for old command versions Issue Type: Improvement Assignee: Unassigned Created: 2016/02/16 9:12 AM Fix Versions: PDB 4.0.0, PDB 3.2.x Priority: Normal Reporter: Andrew Roetker We should deprecated old command versions in master and stable. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-
Jira (PUP-5841) Environment string matching in the parser seems broken
Title: Message Title Henrik Lindberg commented on PUP-5841 Re: Environment string matching in the parser seems broken Note that PUP-5835 is fixed in both 4.3.3 and 4.4.0. 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 (PDB-2426) (MAINT) Pretty query results by default
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2426 (MAINT) Pretty query results by default Change By: Kenneth Barber Scope Change Category: Adopted Scope Change Reason: This is a blocker for release, so we started working on it Fix Version/s: PDB CLI 0.1.0 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 (PDB-2427) (maint) update install modes to get stable tests green
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2427 (maint) update install modes to get stable tests green Change By: Kenneth Barber Scope Change Category: Found Scope Change Reason: Build bug Fix Version/s: PDB 3.2.x 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 (PDB-2429) (maint) this fixes a typo in the setup for installing released PDB
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2429 (maint) this fixes a typo in the setup for installing released PDB Change By: Kenneth Barber Scope Change Category: Found Scope Change Reason: Bug Fix Version/s: PDB 3.2.x 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-5841) Environment string matching in the parser seems broken
Title: Message Title Henrik Lindberg commented on PUP-5841 Re: Environment string matching in the parser seems broken On master I get this: bundle exec puppet apply pup5841.pp Notice: Scope(Class[main]): double colon environment production Notice: Scope(Class[main]): environment production Notice: Scope(Class[main]): environment dot inspect '"production"' Notice: Scope(Class[main]): production - wo Notice: Scope(Class[main]): man - you really shouldn't have to coerce me to make me do these things This was fixed in PUP-5835 . Marking this as a duplicate. Add Comment
Jira (PUP-5728) Change default parsing of manifest files to UTF-8
Title: Message Title Ethan Brown commented on PUP-5728 Re: Change default parsing of manifest files to UTF-8 Ah yeah, I understand now what you were trying to do. Unfortunately that also works around the Ruby behavior the PR addresses. (Ruby previously converted the manifest to the local codepage when reading the file - but if the local codepage is set to UTF8 (65001), then there are no conversion problems) I can tell you that if you use ConEmu, it should display Unicode characters correctly, even when the local codepage is set to 437 and not 65001. 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-5902) Type mismatch describer should expand aliases
Title: Message Title Henrik Lindberg commented on PUP-5902 Re: Type mismatch describer should expand aliases Sure, as long as it is short it can be done textually. The idea for dot output was that text could say - dumped output graph to /tmp/typediff-4563.svg. That behaviour could be behind a feature switch. It could naturally dump in some other format too (for integration purposes). Agree to the textual improvments; better enum explanation, showing expansion unless very long; otoh, what would it have done if the type was very complex without the alias? Maybe expand only on the failing branch? I mean, an alias can contain references to other aliases, if validation got past one of those, they need not be expanded, same for types it has not yet gotten too - i.e. only expand the branch(es) that really needs to be expanded. 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-5728) Change default parsing of manifest files to UTF-8
Title: Message Title Ryan Gard commented on PUP-5728 Re: Change default parsing of manifest files to UTF-8 Ethan Brown The codepage was set to 65001 so that the console would properly display Unicode characters for verification reasons. I'll retest with 437 today just to make sure. 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 (FACT-1340) Update Facter Acceptance tests for cisco-5
Title: Message Title Kenn Hussey assigned an issue to Stan Duffy Facter / FACT-1340 Update Facter Acceptance tests for cisco-5 Change By: Kenn Hussey Assignee: Stan Duffy 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-5804) Update Puppet Acceptance tests for cisco-5
Title: Message Title Kenn Hussey assigned an issue to Stan Duffy Puppet / PUP-5804 Update Puppet Acceptance tests for cisco-5 Change By: Kenn Hussey Assignee: Stan Duffy 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 (FACT-1340) Update Facter Acceptance tests for cisco-5
Title: Message Title Kenn Hussey commented on FACT-1340 Re: Update Facter Acceptance tests for cisco-5 Stan Duffy does the outcome from Friday's meeting affect whether we'll be merging this PR? 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-5804) Update Puppet Acceptance tests for cisco-5
Title: Message Title Kenn Hussey commented on PUP-5804 Re: Update Puppet Acceptance tests for cisco-5 Stan Duffy what was the outcome of the meeting? Have we decided on a different approach here? 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-4497) Yum package provider: ensure => latest fails when obsoleted packages are present
Title: Message Title
Dan Sajner commented on PUP-4497
Re: Yum package provider: ensure => latest fails when obsoleted packages are present
Hi. There is another scenario where the yum provider fails to ensure => latest on a package due to the output from `yum check-update`.
/bin/yum check-update
...
phantomjs.x86_64 2.0.0-1el7 prod-channel-rhel7
Update notice CL-EA-: (from rhel-7-optional) is broken, or a bad duplicate, skipping.
You should report this problem to the owner of the prod-rhel-7-optional repository.
Update notice CL-EA-: (from rhel-7-optional) is broken, or a bad duplicate, skipping.
Update notice CL-BA-: (from rhel-7-optional) is broken, or a bad duplicate, skipping.
puppet apply -e "package{'jenkins': ensure => 'latest'}"
Jira (PUP-1206) Augeas lenses in modules are not loaded when using puppet apply
Title: Message Title
Philipp Gassmann commented on PUP-1206
Re: Augeas lenses in modules are not loaded when using puppet apply
The workaround is to manually emulate pluginsync: https://ask.puppetlabs.com/question/4645/puppet-apply-and-pluginsync/
I added the following code for our masterless puppet setup (in site.pp)
# Workaround for not loading augeas lenses with puppet apply
# https://tickets.puppetlabs.com/browse/PUP-1206
# Emulate pluginsync, https://ask.puppetlabs.com/question/4645/puppet-apply-and-pluginsync/
file { $::settings::libdir:
ensure => directory,
source => 'puppet:///plugins',
recurse => true,
purge => true,
backup => false,
noop=> false,
Jira (PUP-5898) Data types seems to be messed up on hash parameters
Title: Message Title Thomas Hallgren commented on PUP-5898 Re: Data types seems to be messed up on hash parameters Given the simplicity of the fix, and the negative impact of the bug, shouldn't this go into 3.x? 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-5902) Type mismatch describer should expand aliases
Title: Message Title Thomas Hallgren commented on PUP-5902 Re: Type mismatch describer should expand aliases That's way cool, but it's rather hard to present in a terminal window or in a log in general. IMO, this belongs more in the tooling domain (Geppetto or other graphical tool. Stackhammer comes to mind ). The Puppet mismatch describer is all about presenting short concise textual terminal-targeted messages that, of course, helps the user as much as possible. So, perhaps this issue is actually about three things? 1. Better messages when reporting Enum mismatches (this relates to PUP-5901) 2. Alias expansion when reporting (probably controlled by length threshold) 3. Integration points between the Puppet runtime and a graphical debugger. 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.
