Jira (PUP-8606) Module-defined data types are very verbose when displayed
Title: Message Title Thomas Hallgren commented on PUP-8606 Re: Module-defined data types are very verbose when displayed This looks like a bug to me. An Object type should represent itself with its name only, not the full spec. The type in the example should present itself as: TargetSpec = Boltlib::TargetSpec = Variant[String[1], Target, Array[Boltlib::TargetSpec]] Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1841) Facter does not like rto_min in ip route output
Title: Message Title Slava Markeyev created an issue Facter / FACT-1841 Facter does not like rto_min in ip route output Issue Type: Bug Assignee: Unassigned Created: 2018/03/23 3:37 PM Priority: Normal Reporter: Slava Markeyev On Ubuntu 14.04: Warning: Facter: Could not process routing table entry: Expected a destination followed by key/value pairs, got '10.32.64.0/20 via 10.32.68.1 dev eth0 rto_min lock 150ms' Add Comment
Jira (PUP-8606) Module-defined data types are very verbose when displayed
Title: Message Title Henrik Lindberg commented on PUP-8606 Re: Module-defined data types are very verbose when displayed Michael Smith Ok, got it - you get the signature and want to display parameters. Thomas Hallgren can types like Target be made to show less information by default, or should we have a special (polymorph) function to get the desired strings? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8589) Puppet apply or agent should list hiera keys, values and their paths
Title: Message Title Henrik Lindberg commented on PUP-8589 Re: Puppet apply or agent should list hiera keys, values and their paths Naeem Output like you suggest is too simplistic - many lookup results are composed out of multiple paths from multiple locations (a deep merge for example resulting in a hash, a merge with knockout values that removes information, a value that is composed out of interpolation of other lookups, etc. etc. A backend has access to the explain feedback and can produce its own set of information - it may for instance operate on a complex key, it may have its own kind of hierarchy and set of paths. It is simply not doable to reduce it to the simple information you want as it will be wrong in a very large percentage of all lookups. So - I don't see that we can provide that in puppet. You will naturally face the same challenge if you want to attempt to simplify the result of explanations down to that. It may work in your particular case if you are not using deep merges, aliases, or any fancy backends. I am not sure how much work it would be to support a combination of --explain-all and --compile, (not sure if it perhaps already works by just using --explain and --compile. By also specifying a log destination that ends with .json you could perhaps get all of the explain output logged to that file. (I have not tried, in theory it could work). If that does not work, we may need to tweak the implementation we have. Naturally, we need to prioritize such a feature against all other features being requested. If we do prioritize this it will be to "better support understanding and debugging hiera lookup used when compiling" and I think we need to really understand what that means - given that it is not doable to reduce it to the simple case you wish is it really meaningful to dump all of the information - did that just lead to exchanging one problem for another? What is a good user interface in this case? etc. I added this ticket to our Epic for things to consider for Puppet in the 6.y series. However, I don't think it is clear yet how a better debugging support would actually work (given all the things I already commented on). Add Comment
Jira (PUP-8552) Make dnf default for fedora, and systemd default for ubuntu/debian
Title: Message Title Melissa Stone commented on PUP-8552 Re: Make dnf default for fedora, and systemd default for ubuntu/debian The blacklist is https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/upstart.rb#L19 currently we have https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/systemd.rb#L28 defaultfor :operatingsystem => :ubuntu, :operatingsystemmajrelease => ["15.04","15.10","16.04","16.10","17.04","17.10","18.04"] which we should be able to change to defaultfor :operatingsystem => :ubuntu the failing test is https://github.com/puppetlabs/puppet/blob/master/spec/unit/provider/service/systemd_spec.rb#L122 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8606) Module-defined data types are very verbose when displayed
Title: Message Title
Michael Smith commented on PUP-8606
Re: Module-defined data types are very verbose when displayed
This happens when we get a list of parameters on a plan via PAL: https://github.com/puppetlabs/bolt/blob/0.18.0/lib/bolt/pal.rb#L204-L225 We iterate over the parameters and get a printable representation of the type. Is there a way to modify the Target and Error types so they aren't expanded? Currently they appear to be, which is where most of the verbosity comes from. Right now, Target is getting printed as
Object[{name => 'Target', attributes => {'uri' => String[1], 'options' => {type => Hash[String[1], Data], value => {}}}, functions => {'host' => Callable[[0, 0], String[1]], 'name' => Callable[[0, 0], String[1]], 'password' => Callable[[0, 0], Optional[String[1]]], 'port' => Callable[[0, 0], Optional[Integer]], 'protocol' => Callable[[0, 0], Optional[String[1]]], 'user' => Callable[[0, 0], Optional[String[1]]]}}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are
Jira (PUP-8552) Make dnf default for fedora, and systemd default for ubuntu/debian
Title: Message Title Kris Bosland commented on PUP-8552 Re: Make dnf default for fedora, and systemd default for ubuntu/debian Could you add more background to this ticket? Where is the blacklist? Where are the platform restrictions? What tests fail when the restrictions are removed? Thanks! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8606) Module-defined data types are very verbose when displayed
Title: Message Title Henrik Lindberg commented on PUP-8606 Re: Module-defined data types are very verbose when displayed It may also be that we need to support a way to define a useful to_s implementation for registered types that should be opaque. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8606) Module-defined data types are very verbose when displayed
Title: Message Title Henrik Lindberg commented on PUP-8606 Re: Module-defined data types are very verbose when displayed I commented on your commit. I don't think it is a good idea to add a member variable to every type in the type system to hold the source text if that type was obtained from a parameter type _expression_. What is the problem you are trying to solve (apart from the string form being verbose as shown) - where/why do you end up with that particular string output? In general, there is obviously a trade off between being succinct (only showing a type alias for example), vs. showing all of the details. At first we only showed the alias, but then we got complaints that the output was too opaque. You may want to have your own function for determining how much to show - in this case TargetSpec is supposed to be a well known type, as opposed to something a user invented, and you may want to format different types with varying degree of detail/expansion. That is just impossible to have in the types themselves as it depends on the use case / context. (Often a to_s is where such conflicting requirements meet). To give a good recommendation what to do in your case depends on the details of where/when in occurs. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs.
Jira (BOLT-102) Loading params from file on powershell triggers splat operator error
Title: Message Title Michael Smith assigned an issue to Kate Lopresti Puppet Task Runner / BOLT-102 Loading params from file on powershell triggers splat operator error Change By: Michael Smith Assignee: Kate Lopresti Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2997) Logdest cannot be set in the puppet.conf
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2997 Logdest cannot be set in the puppet.conf Change By: Charlie Sharpsteen Affects Version/s: PUP 4.10.10 Affects Version/s: PUP 5.5.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2997) Logdest cannot be set in the puppet.conf
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-2997 Logdest cannot be set in the puppet.conf Change By: Eric Sorenson Team: Agent Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2997) Logdest cannot be set in the puppet.conf
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-2997 Logdest cannot be set in the puppet.conf Change By: Eric Sorenson Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2997) Logdest cannot be set in the puppet.conf
Title: Message Title Robert J commented on PUP-2997 Re: Logdest cannot be set in the puppet.conf Amazing that people are requesting this and Puppetlabs has deemed it not worth fixing. There are some pretty good reasons WHY using the CLI is not a good workaround which have already been stated. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4682) Deprecate Cisco types/providers
Title: Message Title Josh Cooper commented on PUP-4682 Re: Deprecate Cisco types/providers fyi, we'll be removing the interface, vlan and router types out of core in PUP-8575 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8566) "puppet config print" needs --quiet option to disable new (default) verbosity
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8566 "puppet config print" needs --quiet option to disable new (default) verbosity Change By: Josh Cooper Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8566) "puppet config print" needs --quiet option to disable new (default) verbosity
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8566 "puppet config print" needs --quiet option to disable new (default) verbosity Change By: Josh Cooper Fix Version/s: PUP 5.5.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8566) "puppet config print" needs --quiet option to disable new (default) verbosity
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8566 "puppet config print" needs --quiet option to disable new (default) verbosity Change By: Josh Cooper Team: Platform Core Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8566) "puppet config print" needs --quiet option to disable new (default) verbosity
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8566 "puppet config print" needs --quiet option to disable new (default) verbosity Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8606) Module-defined data types are very verbose when displayed
Title: Message Title Michael Smith commented on PUP-8606 Re: Module-defined data types are very verbose when displayed An example of adding original text to the type at https://github.com/MikaelSmith/puppet/tree/PUP-8606. However I'm concerned about the memory implications of doing that on every type. I haven't dug into how else create_param_type is used. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8606) Module-defined data types are very verbose when displayed
Title: Message Title
Michael Smith created an issue
Puppet / PUP-8606
Module-defined data types are very verbose when displayed
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/03/23 12:54 PM
Priority:
Normal
Reporter:
Michael Smith
As noted in BOLT-413, the printable representation for certain data types is very verbose. For example, TargetSpec defined as an alias in Bolt displays as
TargetSpec = Boltlib::TargetSpec = Variant[String[1], Object[{name => 'Target', attributes => {'uri' => String[1], 'options' => {type => Hash[String[1], Data], value => {}}}, functions => {'host' => Callable[[0, 0], String[1]], 'name' => Callable[[0, 0], String[1]], 'password' => Callable[[0, 0], Optional[String[1]]], 'port' => Callable[[0, 0], Optional[Integer]], 'protocol' => Callable[[0, 0], Optional[String[1]]], 'user' => Callable[[0, 0], Optional[String[1]]]}}], Array[Boltlib::TargetSpec]]
This can be seen by running bolt plan show canary in Bolt 0.18.1 (once we get BOLT-407 fixed). I'd rather this use a succinct representation, like TargetSpec or TargetSpec = Bolt::TargetSpec. I see two possibilities for fixing this:
a way to define how the Bolt::TargetSpec type should be displayed via to_s
provide the original parameter text from the plan declaration as part of the type returned via the params_type accessor on a plan.
Jira (BOLT-413) Displaying certain types is overly verbose
Title: Message Title
Michael Smith created an issue
Puppet Task Runner / BOLT-413
Displaying certain types is overly verbose
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/03/23 12:48 PM
Priority:
Normal
Reporter:
Michael Smith
Displaying types like TargetSpec, Target, and Error display the type as an object made up of its component parts rather than the type name. As opposed to other types like Hash, which will display as Hash (rather than Hash[Any, Any] as is implied). For example, TargetSpec displays as
PARAMETERS
- nodes: TargetSpec = Boltlib::TargetSpec = Variant[String[1], Object[{name => 'Target', attributes => {'uri' => String[1], 'options' => {type => Hash[String[1], Data], value => {}}}, functions => {'host' => Callable[[0, 0], String[1]], 'name' => Callable[[0, 0], String[1]], 'password' => Callable[[0, 0], Optional[String[1]]], 'port' => Callable[[0, 0], Optional[Integer]], 'protocol' => Callable[[0, 0], Optional[String[1]]], 'user' => Callable[[0, 0], Optional[String[1]]]}}], Array[Boltlib::Target
Spec]]
We would prefer to display something close to the original text of the plan declaration, i.e. TargetSpec.
Jira (BOLT-407) Using TargetSpec in plan parameters breaks `bolt plan show`
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-407 Using TargetSpec in plan parameters breaks `bolt plan show` Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8589) Puppet apply or agent should list hiera keys, values and their paths
Title: Message Title Naeem commented on PUP-8589 Re: Puppet apply or agent should list hiera keys, values and their paths Thanks for the quick response. I understand that --explain does the job but it also gives you the output of all the hiera data paths it is traversing through to lookup the hiera keys. What we are thinking that if we could get the simplified output like below: Key name Key value Path the key and value was found If this is not easily doable then your suggestion about --explain-all might work as well with some post processing on our side (which we are trying to avoid). How much time do you anticipate it might take to get this feature in. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8562) File performance nearly twice as slow after update
Title: Message Title Josh Cooper assigned an issue to Melissa Stone Puppet / PUP-8562 File performance nearly twice as slow after update Change By: Josh Cooper Assignee: Josh Cooper Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8597) Modify rich data serialization to use shorter tags instead of __pcore_type__
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8597 Modify rich data serialization to use shorter tags instead of __pcore_type__ Change By: Henrik Lindberg Release Notes Summary: The earlier rich data format used the tags __pcore_type__ and __pcore_value__, these are now shortened to __ptype and __pvalue respectively. Sprint: Platform Core KANBAN Release Notes: Deprecation Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group
Jira (PUP-8597) Modify rich data serialization to use shorter tags instead of __pcore_type__
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-8597 Modify rich data serialization to use shorter tags instead of __pcore_type__ Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1952) Run specs against jruby
Title: Message Title Eric Delaney updated an issue Puppet / PUP-1952 Run specs against jruby Change By: Eric Delaney Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6996) Puppet automatically creates the production environment with the incorrect permissions
Title: Message Title Eric Delaney updated an issue Puppet / PUP-6996 Puppet automatically creates the production environment with the incorrect permissions Change By: Eric Delaney QA Risk Assessment: Needs Assessment Manual Release Notes Summary: If the production environment did not exist when puppet is run, it would create the directory as the user root and group root instead of the service account if its available. Puppet nows set the owner and group to the service account if it exists on the node. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To
Jira (PUP-4020) Add a Like type to specify a type being the type of a resource parameter
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4020 Add a Like type to specify a type being the type of a resource parameter Change By: Henrik Lindberg Fix Version/s: PUP 5.y Fix Version/s: PUP 6.y Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-372
Associate jobs with plans when using the PCP transport
Change By:
Alex Dreyer
During the first action that uses the PCP transport with a new config while running a plan attempt to use {{/commands/plan_start}} (providing the plan name of the top level plan called from the CLI, parameters and description to orch) to get a plan_job_id. If the command is not supported by Orchestrator, continue without a plan_job_id and use the {{task}} command instead of {{plan_task}}. Other errors should halt the plan.The plan job id should be logged at notice level.Subsequent actions over the PCP transport with the same config should use the same plan_job_id.On completion] Bolt should call {{/commands/plan_end}} for every orchestrator it's tracking a {{plan_job_id}} for. This indicates that transports need a concept of setup and teardown and the orchestrator transport needs to track "connections". Teardown should not be called on control+c.The name and parameters of nested plans are essentially ignored by the PCP transport. Only the plan named from the CLI should be used. Executor will need to pass information about the CLI invocation to transports to support this. It needs to know if it is running as part of a plan and if so what the plan info is. We may be able to simplify some logging using this too.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-372
Associate jobs with plans when using the PCP transport
Change By:
Alex Dreyer
During the first action that uses the PCP transport with a new config while running a plan attempt to use {{/commands/plan_start}} (providing the plan name of the top level plan called from the CLI, parameters and description to orch) to get a plan_job_id. If the command is not supported by Orchestrator, continue without a plan_job_id and use the {{task}} command instead of {{plan_task}}. Other errors should halt the plan.The plan job id should be logged at notice level.Subsequent actions over the PCP transport with the same config should use the same plan_job_id.On completion] Bolt should call {{/commands/plan_end}} for every orchestrator it's tracking a {{plan_job_id}} for. This indicates that transports need a concept of setup and teardown and the orchestrator transport needs to track "connections". Teardown should not be called on control+c.The name and parameters of nested plans are essentially ignored by the PCP transport. Only the plan named from the CLI should be used.Executor will need to pass information about the CLI invocation to transports to support this. It needs to know if it is running as part of a plan and if so what the plan info is. We may be able to simplify some logging using this too. Plan descriptions are out of scope for this ticket. It will eventually be a CLI --description argument (see BOLT-410)
Add Comment
This message was sent
Jira (BOLT-410) run_* functions should accept a description
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-410
run_* functions should accept a description
Change By:
Alex Dreyer
In plans that run the same tasks or command repeatedly users often end up logging simple messages to inform the user in more human readable terms what is happening.{noformat}notice("deploying application")run_task(package, $targets, action ="" install, version => $version, name => my_app){noformat}run_* functions should accept an options string argument description. This argument should be used in summary log messages and passed to orchestrator.{noformat}run_task(package, $targets, "deploying application", action ="" install, version => $version, name => my_app){noformat}These descriptions will also make it easier to write tests{noformat}expect_task('package').with_description_matching(/deploying application/).called_times(5){noformat}Cli should accept {{ --description }} for run task, command, script, and file_upload endpoints. {{ --description }} for plan run should be added if BOLT-372 is complete
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-410) run_* functions should accept a description
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-410
run_* functions should accept a description
Change By:
Alex Dreyer
In plans that run the same tasks or command repeatedly users often end up logging simple messages to inform the user in more human readable terms what is happening.{noformat}notice("deploying application")run_task(package, $targets, action ="" install, version => $version, name => my_app){noformat}run_* functions should accept an options string argument description. This argument should be used in summary log messages and passed to orchestrator.{noformat}run_task(package, $targets, "deploying application", action ="" install, version => $version, name => my_app){noformat}These descriptions will also make it easier to write tests{noformat}expect_task('package').with_description_matching(/deploying application/).called_times(5){noformat}Cli should accept {{--description}} for run task, command, script, and file_upload endpoints. {{ --description }} for plan run should be added if BOLT-372 is complete
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-410) run_* functions should accept a description
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-410
run_* functions should accept a description
Change By:
Alex Dreyer
In plans that run the same tasks or command repeatedly users often end up logging simple messages to inform the user in more human readable terms what is happening.{noformat}notice("deploying application")run_task(package, $targets, action ="" install, version => $version, name => my_app){noformat}run_* functions should accept an options string argument description. This argument should be used in summary log messages and passed to orchestrator.{noformat}run_task(package, $targets, "deploying application", action ="" install, version => $version, name => my_app){noformat}These descriptions will also make it easier to write tests{noformat}expect_task('package').with_description_matching(/deploying application/).called_times(5){noformat} Cli should accept {{--description}} for run task, command, script, and file_upload endpoints. --description for plan run should be added if BOLT-372 is complete
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-372
Associate jobs with plans when using the PCP transport
Change By:
Alex Dreyer
During the first action that uses the PCP transport with a new config while running a plan attempt to use {{/commands/plan_start}} (providing the plan name of the top level plan called from the CLI, parameters and description to orch ) to get a plan_job_id. If the command is not supported by Orchestrator, continue without a plan_job_id and use the {{task}} command instead of {{plan_task}} . Other errors should halt the plan. The plan job id should be logged at notice level. Subsequent actions over the PCP transport with the same config should use the same plan_job_id.On completion , error, or Ctrl-C, ] Bolt should call {{/commands/plan_end}} if for every orchestrator it's tracking a {{ plan_start plan_job_id }} was previously used for . This indicates that transports need a concept of setup and teardown and the orchestrator transport needs to track "connections" . Teardown should not be called on control+c. The name and parameters of nested plans are essentially ignored by the PCP transport. Executor will need to pass information about the CLI invocation to transports to support this. It needs to know if it is running as part of a plan and if so what the plan info is.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-407) Using TargetSpec in plan parameters breaks `bolt plan show`
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-407 Using TargetSpec in plan parameters breaks `bolt plan show` Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-412) Explore running puppet device operations from a Bolt plan
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-412 Explore running puppet device operations from a Bolt plan Change By: Michael Smith Summary: Run Explore running puppet device operations from a Bolt plan Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-412) Run puppet device operations from a Bolt plan
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-412 Run puppet device operations from a Bolt plan Issue Type: Story Assignee: Unassigned Created: 2018/03/23 9:28 AM Priority: Normal Reporter: Michael Smith puppet device is a mode of Puppet that's more akin to Bolt's remote execution model than anything else in Puppet. Explore using puppet device from a Bolt plan to operate on network devices. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-411) Update windows install instructions
Title: Message Title Jenny Mahmoudi created an issue Puppet Task Runner / BOLT-411 Update windows install instructions Issue Type: Improvement Assignee: Kate Lopresti Components: DOCS Created: 2018/03/23 9:06 AM Priority: Normal Reporter: Jenny Mahmoudi We should call out that Windows install steps should be done from Powershell, not a ruby session. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8562) File performance nearly twice as slow after update
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8562 File performance nearly twice as slow after update Change By: Josh Cooper Fix Version/s: PUP 5.3.6 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8562) File performance nearly twice as slow after update
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8562 File performance nearly twice as slow after update Change By: Josh Cooper Affects Version/s: PUP 5.3.4 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-410) run_* functions should accept a description
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-410 run_* functions should accept a description Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-410) run_* functions should accept a description
Title: Message Title
Alex Dreyer created an issue
Puppet Task Runner / BOLT-410
run_* functions should accept a description
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2018/03/23 8:44 AM
Priority:
Normal
Reporter:
Alex Dreyer
In plans that run the same tasks or command repeatedly users often end up logging simple messages to inform the user in more human readable terms what is happening.
notice("deploying application")
run_task(package, $targets, action ="" install, version => $version, name => my_app)
run_* functions should accept an options string argument description. This argument should be used in summary log messages and passed to orchestrator.
run_task(package, $targets, "deploying application", action ="" install, version => $version, name => my_app)
These descriptions will also make it
Jira (PUP-8605) Move functions unique, reject, and sort from stdlib to puppet
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8605 Move functions unique, reject, and sort from stdlib to puppet Issue Type: Improvement Assignee: Unassigned Created: 2018/03/23 8:13 AM Priority: Normal Reporter: Henrik Lindberg Move functions unique, reject, and sort from stdlib to puppet and update them to use the 4.x function API. The new implementation must be backwards compatible but may add new features. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8604) Move String functions upcase, downcase, capitalize, camelcase, lstrip, rstrip, strip, chop, chomp from stdlib to puppet
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8604 Move String functions upcase, downcase, capitalize, camelcase, lstrip, rstrip, strip, chop, chomp from stdlib to puppet Change By: Henrik Lindberg Sub-team: Language Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8604) Move String functions upcase, downcase, capitalize, camelcase, lstrip, rstrip, strip, chop, chomp from stdlib to puppet
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8604 Move String functions upcase, downcase, capitalize, camelcase, lstrip, rstrip, strip, chop, chomp from stdlib to puppet Issue Type: Improvement Assignee: Unassigned Created: 2018/03/23 8:12 AM Priority: Normal Reporter: Henrik Lindberg Move String functions upcase, downcase, capitalize, camelcase, lstrip, rstrip, strip, chop, chomp from stdlib to puppet and update them to the 4.x function API. The new implementations must be backwards compatible but may add new features. If possible implement these by using StringConverter functionality. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8603) Move math functions abs, ceil, floor, round, min, max from stdlib to puppet
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8603 Move math functions abs, ceil, floor, round, min, max from stdlib to puppet Issue Type: Improvement Assignee: Unassigned Created: 2018/03/23 8:09 AM Labels: help_wanted Priority: Normal Reporter: Henrik Lindberg The math functions abs, ceil, floor, round, min, max should be moved from stdlib to puppet and be modernized to the 4.x function API. They must be backwards compatible but can be extended in functionality where wanted (for example supporting array arguments if not already supported in current implementation). Add Comment
Jira (PUP-8602) Normalize/validate catalogs for PDB
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8602 Normalize/validate catalogs for PDB Issue Type: Improvement Assignee: Unassigned Created: 2018/03/23 8:02 AM Priority: Normal Reporter: Henrik Lindberg Currently catalogs are post-processed by PDB to normalize them and to clean up certain (old?) constructs. As we now have validation (of some things) in the catalog that we did not use to have (dangling references to resources etc) it seems possible to produce catalogs that do not require as much post processing. The work in this ticket is to list all of the validations and other requirements required to be able to minimize the amount of PDB post processing (if possible not require any at all). Ping Russell Mull Add Comment
Jira (PUP-8601) agent should support rich data content negotiation
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8601 agent should support rich data content negotiation Issue Type: Improvement Assignee: Unassigned Created: 2018/03/23 7:56 AM Priority: Normal Reporter: Henrik Lindberg The 6.0 agent should request a catalog using a rich-data encoding by default. The request rather than the current --rich-data setting should control the format of the catalog. (The setting is still needed but it should default to true for command line execution). An agent < 6.0 when talking to a server >= 6.0.0 not know how to request rich data format (now it assumes rich data if it has --rich-data turned on. I think it is safe to assume that we can simply ignore the --rich-data flag on the agent side and state that in order to use rich-data you need to use a 6.y agent. Further - in the current protocol, we change the encoding from JSON (the default) to PSON if we detect ASCII-8bit String data. With rich-data encoding we should not do this. There are options: (Magically) transform the ASCII-8bit String to a Binary - the agent will need to be able to deal with an instance of Binary (our File resource will be able to do so). Raise an error and tell user to use a Binary instead of an ASCII-8bit (Magically) deserialize a Binary to ASCII-8bit on the agent side to allow types and providers that are unaware of the Binary type work as they did before. (This has bad side effects further downstream in reports etc). Number 2 is the preferred (non magical) solution.
Jira (PUP-2354) agent is confused about cert state
Title: Message Title Tama MA commented on PUP-2354 Re: agent is confused about cert state Is there anyway to get rid of SSL altogether? +My entire cluster runs on top of VPN, so I do not need SSL from puppet. Otherwise, I will need allow_duplicate_certs = true to work on agents. It is really unproductive to delete certs from the master, everytime I vagrant destroy / up couple of nodes per day. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8600) plugin-sync the data-types from all modules
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8600 plugin-sync the data-types from all modules Issue Type: Improvement Assignee: Unassigned Created: 2018/03/23 7:39 AM Priority: Normal Reporter: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-8599) make data types defined in modules available to puppet agent
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8599 make data types defined in modules available to puppet agent Issue Type: Improvement Assignee: Unassigned Created: 2018/03/23 7:38 AM Priority: Normal Reporter: Henrik Lindberg To make data types defined in modules available to the agent the loaders needs to be configured to include information in the plugin-synced modules. (Another ticket defines the work to get the data types plugin-synced). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8598) make 4.x loaders available to puppet agent
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8598 make 4.x loaders available to puppet agent Issue Type: Improvement Assignee: Unassigned Created: 2018/03/23 7:36 AM Priority: Normal Reporter: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-8597) Modify rich data serialization to use shorter tags instead of __pcore_type__
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8597 Modify rich data serialization to use shorter tags instead of __pcore_type__ Issue Type: Improvement Assignee: Unassigned Created: 2018/03/23 7:31 AM Priority: Normal Reporter: Henrik Lindberg Serialization of rich data in JSON/YAML is currently using the tags: __pcore_type__ __pcore_value__ Those are longer than they need to be for making them unique/non-clashing with normal attributes. We should shorten those to: __ptype __pvalue When writing, but continue to support the longer tags when reading.
Jira (PUP-6344) metrics.time.total does not correlate to time reported in log
Title: Message Title Charlie Sharpsteen commented on PUP-6344 Re: metrics.time.total does not correlate to time reported in log Melissa Stone Seems like the question is whether the missing 5 seconds is occurring before the call to run_internal or after it. A quick way to measure would be adding something like puts Time.now.to_f to: /opt/puppetlabs/puppet/bin/puppet Adding one before Puppet is loaded via `require 'puppet'`, before CommandLine is executed, and then after would give some good indications along with similar puts statements around the run_internal method. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2968) Make it possible to namespace ruby-defined custom types
Title: Message Title David Schmitt commented on PUP-2968 Re: Make it possible to namespace ruby-defined custom types Some notes from a initial design and brainstorming session with Henrik Lindberg: puppet generate types; modify type name in generated output; see what breaks, might come up through 4x loaders there is a optimisation somewhere avoiding type lookup when a qualified name is encountered agent side: problematic because of the type <-> class mapping. Needs breaking up. Maybe possible to inject a switch to lookup new-style types when namespaced typenames. how does rspec-puppet, and PE console react to namespaced resources? puppet generate types output could already stand alone for the server, would need more scaffolding on the agent, see CompilableResourceType better: define a puppet datatype instead, mark it through inheritance from a marker type; similar to Struct Loaders: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/pops/loaders.rb smartpaths: https://github.com/puppetlabs/puppet/blob/e7839794a1d7d393e6716927764c1276494123c2/lib/puppet/pops/loader/loader_paths.rb pluginsync also needs to be modified to download the required information Add Comment
Jira (PUP-8589) Puppet apply or agent should list hiera keys, values and their paths
Title: Message Title Henrik Lindberg commented on PUP-8589 Re: Puppet apply or agent should list hiera keys, values and their paths I think we have another ticket where it is asked that an agent can ask for --explain without having to turn on debugging on the server side. You would then end up with the explain output in the log. Would that be sufficient? I doubt that a much simpler format for the explain output is really doable (without loss of fidelity) as the backends can be quite complex along with all the processing that hiera can do (merges, defaults, aliases etc.) You can also use the lookup CLI with --explain and use --compile to compile a catalog - maybe we should augment that with something like an --explain-all. You could then get all of it as JSON for post processing with some json queries. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8596) Add support for CatalogCompiler in PAL
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8596 Add support for CatalogCompiler in PAL Issue Type: New Feature Assignee: Unassigned Created: 2018/03/23 6:53 AM Priority: Normal Reporter: Henrik Lindberg Currently PAL only supports ScriptCompiler, it should also support a CatalogCompiler. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8595) PAL API in 6.y
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8595 PAL API in 6.y Change By: Henrik Lindberg Fix Version/s: PUP 6.y Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8595) PAL API in 6.y
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8595 PAL API in 6.y Issue Type: Epic Assignee: Unassigned Created: 2018/03/23 6:49 AM Priority: Normal Reporter: Henrik Lindberg The PAL (Puppet As a Library) was added in Puppet 5.5.0. This Epic is for continued work for PAL - supporting Bolt with high level API to puppet, but also evolving into the main way the language/compiler is used via a well defined public API. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8168) Puppet as a Library (PAL) features for Puppet 5.y
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8168 Puppet as a Library (PAL) features for Puppet 5.y Change By: Henrik Lindberg Fix Version/s: PUP 5.5.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8206) loader.discover(:type) returns multiple instances of the same thing
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-8206 loader.discover(:type) returns multiple instances of the same thing Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8594) Specify injection of compiler in function API (added in PUP-8237)
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8594 Specify injection of compiler in function API (added in PUP-8237) Change By: Henrik Lindberg Release Notes Summary: It is now possible to get the compiler as an injected parameter in the 4.x function API. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8594) Specify injection of compiler in function API (added in PUP-8237)
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8594 Specify injection of compiler in function API (added in PUP-8237) Issue Type: Improvement Assignee: Unassigned Created: 2018/03/23 6:43 AM Priority: Normal Reporter: Henrik Lindberg In PUP-8237 injection of a compiler was added as a feature in the function API. This needs to be documented in the 4.x function API specification. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8486) Warning for undefined variables is slow in jruby
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8486 Warning for undefined variables is slow in jruby Change By: Henrik Lindberg Release Notes Summary: Internal performance related issue - not user facing. Sprint: Platform Core KANBAN Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8486) Warning for undefined variables is slow in jruby
Title: Message Title Henrik Lindberg commented on PUP-8486 Re: Warning for undefined variables is slow in jruby I put up a PR - the logic needing change was actually in Puppet - so no need to change the hiera gem. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8486) Warning for undefined variables is slow in jruby
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8486 Warning for undefined variables is slow in jruby Change By: Henrik Lindberg Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8486) Warning for undefined variables is slow in jruby
Title: Message Title Henrik Lindberg assigned an issue to Patrick Carlisle Puppet / PUP-8486 Warning for undefined variables is slow in jruby Change By: Henrik Lindberg Assignee: Patrick Carlisle Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6344) metrics.time.total does not correlate to time reported in log
Title: Message Title Maximilian Philipps commented on PUP-6344 Re: metrics.time.total does not correlate to time reported in log I have no idea how you all get such fast puppets runs, but I at least can confirm the issue. Sometimes we see a large discreptancy between the time reported in the puppet-agent log and in the last_summery.yaml: In this case here the last_summery.yaml reports a total of 2755.9764387860105 seconds, but the puppet-agent log claims to have "only" taken 920.03 seconds. version: config: 5a84cbdc4c7277446118e5c5847bc7ffeee017f3-dirty puppet: 5.5.0 resources: changed: 0 corrective_change: 0 failed: 0 failed_to_restart: 0 out_of_sync: 0 restarted: 0 scheduled: 0 skipped: 0 total: 1971
Jira (PUP-8593) Add alias to lookup_options and make it redirect to lookup of the alias
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8593 Add alias to lookup_options and make it redirect to lookup of the alias Issue Type: New Feature Assignee: Unassigned Created: 2018/03/23 3:56 AM Priority: Normal Reporter: Henrik Lindberg The existing hiera interpolation function alias is problematic to use. By adding a key alias in lookup_options for an original-key a lookup should take that alias-key and use it to lookup instead of the given original-key. Details: The implementation must guard against circular aliases There is an option wrt handling of the other lookup_options: Use the options for original-key and ignore those in alias-key ignore the options for original-key and use those for the alias-key merge the options with original-key at higher t If an alias-key is in turn aliased, the process recurses Option 3 allows for just specifying alias and getting the rest of the options from the aliased key. We can also add advanced features: If the alias-key is an array, the entries in that array are used as aliased lookups and the result is an array with those values. If the alias-key is a hash, the keys are used as keys in the resulting hash where values are the looked up keys
Jira (PUP-6870) 6.y Lookup - potential future work
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6870 6.y Lookup - potential future work Change By: Henrik Lindberg Summary: 5 6 .y Lookup - potential future work Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6870) 5.y Lookup - potential future work
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6870 5.y Lookup - potential future work Change By: Henrik Lindberg Epic Name: 5 6 .y Lookup Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3743) Parser should report invalid operand types when possible
Title: Message Title Henrik Lindberg commented on PUP-3743 Re: Parser should report invalid operand types when possible Closing this as it really needs type inference to be any good - and type inference would be too much of a performance problem at runtime, Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8592) `puppet config --section main print` writes section info to stderr
Title: Message Title Daniel Parks created an issue Puppet / PUP-8592 `puppet config --section main print` writes section info to stderr Issue Type: Bug Affects Versions: PUP 5.5.0 Assignee: Unassigned Created: 2018/03/22 11:30 PM Labels: customer0 Priority: Normal Reporter: Daniel Parks ❯ puppet config --section main print confdir >/dev/null Resolving settings from section 'main' in environment 'production' I already know what section it's from; I don't need to have it print it.
