Jira (FACT-1797) Amazon EC2 C5 Instances not detected as is_virtual causing ec2_metadata fact data not to resolve
Title: Message Title Joshua Keiser updated an issue Facter / FACT-1797 Amazon EC2 C5 Instances not detected as is_virtual causing ec2_metadata fact data not to resolve Change By: Joshua Keiser CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1797) Amazon EC2 C5 Instances not detected as is_virtual causing ec2_metadata fact data not to resolve
Title: Message Title Joshua Keiser updated an issue Facter / FACT-1797 Amazon EC2 C5 Instances not detected as is_virtual causing ec2_metadata fact data not to resolve Change By: Joshua Keiser Method Found: Needs Assessment Customer Feedback Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-263) log bolt results to a log file
Title: Message Title Yasmin Rajabi commented on BOLT-263 Re: log bolt results to a log file One file per node could get unmanageable once you get to 1000s of servers right? Would the logs/results include the node in each line? Its pretty easy (arguably normal) to parse that information in a logstash/splunk type tool if each event has whatever info a user would want to parse by, Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8106) "mount" type should autorequire its mountpoint
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8106 "mount" type should autorequire its mountpoint Change By: Melissa Stone Release Notes Summary: The mount resource now auto requires the file resource that is its mountpoint. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8106) "mount" type should autorequire its mountpoint
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8106 "mount" type should autorequire its mountpoint Change By: Melissa Stone Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5426) config set ignores --section and can insert duplicate settings if they are in [main]
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5426 config set ignores --section and can insert duplicate settings if they are in [main] Change By: Josh Cooper Acceptance Criteria: Using puppet config set doesn't produce a duplicate setting as described in the steps to reproduce. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3020) Add setting delete and setting list add/remove functions to puppet config.
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-3020 Add setting delete and setting list add/remove functions to puppet config. Change By: Josh Cooper Assignee: Ben Ford Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3020) Add setting delete and setting list add/remove functions to puppet config.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3020 Add setting delete and setting list add/remove functions to puppet config. Change By: Josh Cooper Acceptance Criteria: It should be possible to delete/unset a setting from puppet.conf, so that the default value defined in code is used.It should be possible to append a value to a list-type of setting. It should handle the case where the setting is not defined and is already defined with possibly an empty value.It should be possible to remove a value from a list-type of setting. It should handle cases where the setting has more than one value, has only one value, or the value doesn't exist. Removing the last value should not remove the setting.The delimiter for multiple values should depend on the setting type. For example, we use comma for report processors, but File::PATH_SEPARATOR for path settings. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8259) PAL list_tasks doesn't return useful results unless all task metadata is valid
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-8259
PAL list_tasks doesn't return useful results unless all task metadata is valid
Change By:
Michael Smith
By prying into the parser, I If invalid metadata is found , {{ Variant[Enum[yes, no, maybe], Boolean]] list_tasks }} was present in one of my task metadata files will throw an exception . Using PAL We ' s list_tasks wasn't very helpful, as it displayed{code}Error: Syntax error at ']' at line 1:39 on node localhostbundler: failed d like to load command: bolt be able to log tasks that have invalid metadata ( /Users/michaelsmith/puppetlabs/bolt/.bundle/gems/ruby/2.3.0/bin/bolt)Puppet::ParseErrorWithIssue: Syntax error at ']' at line 1:39 on node localhost /Users/michaelsmith/puppetlabs/bolt/vendored/puppet/lib/puppet/pops/parser/parser_support.rb:124: in `on_error' /Users/michaelsmith/puppetlabs/bolt/vendored/puppet/lib/puppet/pops/parser/lexer2 a more controlled method, i . rb:727:in `scan' /Users/michaelsmith/ e . rbenv/versions/2.3.4/lib/ruby/2.3.0/racc/parser.rb:320:in `_racc_yyparse_c' /Users/michaelsmith/.rbenv/versions/2.3.4/lib/ruby/2.3.0/racc/parser.rb:320:in `yyparse' /Users/michaelsmith/puppetlabs/bolt/vendored/puppet/lib/puppet/pops/parser/parser_support.rb:237:in `_parse' /Users/michaelsmith/puppetlabs/bolt/vendored/puppet/lib/puppet/pops/parser/parser_support.rb:131:in `parse_string' /Users/michaelsmith/puppetlabs/bolt/vendored/puppet/lib/puppet/pops/types/type_parser.rb:36:in `parse' /Users/michaelsmith/puppetlabs/bolt/vendored/puppet/lib/puppet/pops/loader/task_instantiator.rb:57:in `block (2 levels catch the exception and print a summary ) in create_task_from_hash' /Users/michaelsmith/puppetlabs/bolt/vendored/puppet/lib/puppet/pops/loader/task_instantiator while still presenting a list of valid tasks . rb:54:in `each_pair' /Users/michaelsmith/puppetlabs/bolt/vendored/puppet/lib/puppet/pops/loader/task_instantiator.rb:54:in `block in create_task_from_hash' /Users/michaelsmith/puppetlabs/bolt/vendored/puppet/lib/puppet/pops/loader/task_instantiator.rb:51:in `each_pair' /Users/michaelsmith/puppetlabs/bolt/vendored/puppet/lib/puppet/pops/loader/task_instantiator.rb:51:in `create_task_from_hash' /Users/michaelsmith/puppetlabs/bolt/vendored/puppet/lib/puppet/pops/loader/task_instantiator.rb:34:in `create_task' /Users/michaelsmith/puppetlabs/bolt/vendored/puppet/lib/puppet/pops/loader/task_instantiator.rb:25:in `create' /Users/michaelsmith/puppetlabs/bolt/vendored/puppet/lib/puppet/pops/loader/module_loaders.rb:243:in `instantiate' /Users/michaelsmith/puppetlabs/bolt/vendored/puppet/lib/puppet/pops/loader/module_loaders.rb:219:in `find' /Users/michaelsmith/puppetlabs/bolt/vendored/puppet/lib/puppet/pops/loader/base_loader.rb:161:in `internal_load' /Users/michaelsmith/puppetlabs/bolt/vendored/puppet/lib/puppet/pops/loader/base_loader.rb:42:in `load_typed' /Users/michaelsmith/puppetlabs/bolt/vendored/puppet/lib/puppet/pops/loader/module_loaders.rb:137:in `block (2 levels) in discover' /Users/michaelsmith/puppetlabs/bolt/vendored/puppet/lib/puppet/pops/loader/module_loaders.rb:134:in `each' /Users/michaelsmith/puppetlabs/bolt/vendored/puppet/lib/puppet/pops/loader/module_loaders.rb:134:in `block in discover'
Jira (PUP-8259) PAL list_tasks doesn't return useful results unless all task metadata is valid
Title: Message Title Michael Smith updated an issue Puppet / PUP-8259 PAL list_tasks doesn't return useful results unless all task metadata is valid Change By: Michael Smith Summary: PAL list_tasks doesn't display file information when parsing error return useful results unless all task metadata is encountered valid Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3020) Add setting delete and setting list add/remove functions to puppet config.
Title: Message Title Josh Cooper commented on PUP-3020 Re: Add setting delete and setting list add/remove functions to puppet config. Managing list values would be useful for things like basemodulepath, supported_checksum_types, serverlist, basically any setting of type :path or :array. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8259) PAL list_tasks doesn't display file information when parsing error is encountered
Title: Message Title Michael Smith commented on PUP-8259 Re: PAL list_tasks doesn't display file information when parsing error is encountered Newer code does provide a clearer error message. I can update this ticket to reflect the need for more fine-grained error handling. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8259) PAL list_tasks doesn't display file information when parsing error is encountered
Title: Message Title Michael Smith commented on PUP-8259 Re: PAL list_tasks doesn't display file information when parsing error is encountered I'll give it a try with newer code. Ideally we'd like to know have clear errors for each task that fails to load, as well as the list of tasks that loaded cleanly. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5710) puppet config "unset"
Title: Message Title Josh Cooper commented on PUP-5710 Re: puppet config "unset" Duplicate of PUP-3020, closing Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3321) config set adds a preceding newline to value if previous value was empty
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3321 config set adds a preceding newline to value if previous value was empty Change By: Josh Cooper Acceptance Criteria: It should be possible to set a puppet setting to an empty value, and later continue to manage settings using "puppet config". Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3374) puppet config print pidfile incorrect for master and agent
Title: Message Title Josh Cooper commented on PUP-3374 Re: puppet config print pidfile incorrect for master and agent Putting this in needs information while we figure out how to provide more context when managing settings for different run modes. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8106) "mount" type should autorequire its mountpoint
Title: Message Title Kris Bosland commented on PUP-8106 Re: "mount" type should autorequire its mountpoint Merged to master https://github.com/puppetlabs/puppet/commit/e0676fb4f7d37ffb3029caf3f310c83ef72fd2a0. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8188) --render-as broken in puppet config print
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8188
--render-as broken in puppet config print
Change By:
Josh Cooper
Acceptance Criteria:
Using the {{render-as}} option with valid values, e.g. {{json}} or {{yaml}}, should generate a valid hash of settings, e.g.{ "key": "value"}or---key: valuePuppet settings only contain values that can be represented as strings, numerics or booleans, so I would expect all of those values to convert to the appropriate JSON or YAML type.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3796) memory leak in reports querying
Title: Message Title Charlie Sharpsteen updated an issue PuppetDB / PDB-3796 memory leak in reports querying Change By: Charlie Sharpsteen CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8264) Schedule and Filebucket resources have a null containing class
Title: Message Title Erik Hansen updated an issue Puppet / PUP-8264 Schedule and Filebucket resources have a null containing class Change By: Erik Hansen Summary: Resources Schedule and Filebucket resources have a null containing class Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8264) Resources have a null containing class
Title: Message Title Erik Hansen created an issue Puppet / PUP-8264 Resources have a null containing class Issue Type: Bug Affects Versions: PUP 4.10.4 Assignee: Unassigned Created: 2017/12/18 3:12 PM Priority: Normal Reporter: Erik Hansen I'm not sure how this happens but it's possible to see Schedule and Filebucket resources that are not contained by any class. I think this might be happening here: https://github.com/puppetlabs/puppet/blob/5.3.3/lib/puppet/resource/catalog.rb#L321-L332 Here is a snippet of a report where one of these events is skipped: "status": "skipped", "timestamp": "2017-12-18T18:00:20.303+00:00",
Jira (PUP-8024) Only load module translations when necessary
Title: Message Title Josh Cooper assigned an issue to Eric Delaney Puppet / PUP-8024 Only load module translations when necessary Change By: Josh Cooper Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8024) Only load module translations when necessary
Title: Message Title Josh Cooper commented on PUP-8024 Re: Only load module translations when necessary Now that PUP-8026 and PUP-8013 are fixed, let's re-run the benchmark and see if the issues are resolved. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8081) Create tests for expanded module I18N testing
Title: Message Title Josh Cooper commented on PUP-8081 Re: Create tests for expanded module I18N testing Most of the expected functionality is in the PR associated with PUP-8080. Updated description to match. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8081) Create tests for expanded module I18N testing
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8081 Create tests for expanded module I18N testing Change By: Josh Cooper Need to create tests for the following I18n and modules cases:* - Module in multiple environments - * Run puppet agent multiple times without restarting the server (not planning on doing this) * - Puppet Functions, custom facts, manifests, types, providers - * - puppet agent - * - puppet apply - * - puppet facts - * - puppet describe - * - puppet resource - * - Can still disable translations globally - * - Verify fall back when language not available - * - server side non-EN locale - Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-258) Configuration options for the PCP transport
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-258
Configuration options for the PCP transport
Change By:
Lucy Wyman
The orchestrator pcp transport should be configurable from the bolt configuration file.example{code}pcp: service-url: cacert ca-cert : token-file: environment:{code}service-url, cacert and token-file should be passed to the OrchestratorClient when it's created. If they are nil or not present they should not passed so defaults in the client library can be used.environment should be passed added to the task command body.User story for environmentWhen a customer's primary environment (or environment relevant to a set of tasks) is ≠ production, it is impossible today to use Bolt and transport=pcp to run a plan using those tasks. Users should be able to configure what environment is sent to orchestrator as part of the task command with the {{task-environment}} configuration option in the pcp section of bolt.yml
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3321) config set adds a preceding newline to value if previous value was empty
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3321 config set adds a preceding newline to value if previous value was empty Change By: Josh Cooper Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7938) I18N Indented and line wrapped face plugin output
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7938 I18N Indented and line wrapped face plugin output Change By: Eric Delaney Sprint: Platform Core Grooming Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8188) --render-as broken in puppet config print
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8188 --render-as broken in puppet config print Change By: Josh Cooper Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5710) puppet config "unset"
Title: Message Title Craig Gomes updated an issue Puppet / PUP-5710 puppet config "unset" Change By: Craig Gomes Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5426) config set ignores --section and can insert duplicate settings if they are in [main]
Title: Message Title Craig Gomes updated an issue Puppet / PUP-5426 config set ignores --section and can insert duplicate settings if they are in [main] Change By: Craig Gomes Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3374) puppet config print pidfile incorrect for master and agent
Title: Message Title Craig Gomes updated an issue Puppet / PUP-3374 puppet config print pidfile incorrect for master and agent Change By: Craig Gomes Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3321) config set adds a preceding newline to value if previous value was empty
Title: Message Title Craig Gomes updated an issue Puppet / PUP-3321 config set adds a preceding newline to value if previous value was empty Change By: Craig Gomes Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-119) Implement `--noop` commandline flag and API support for noop tasks
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-119 Implement `--noop` commandline flag and API support for noop tasks Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3020) Add setting delete and setting list add/remove functions to puppet config.
Title: Message Title Craig Gomes updated an issue Puppet / PUP-3020 Add setting delete and setting list add/remove functions to puppet config. Change By: Craig Gomes Sprint: Platform Core Hopper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-252) Run Bolt acceptance tests on merge
Title: Message Title Michael Smith assigned an issue to Zach Reichert Puppet Task Runner / BOLT-252 Run Bolt acceptance tests on merge Change By: Michael Smith Assignee: Zach Reichert Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-252) Run Bolt acceptance tests on merge
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-252 Run Bolt acceptance tests on merge Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-190) Tasks in subfolders of a module are incorrectly loaded from plans
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-190 Tasks in subfolders of a module are incorrectly loaded from plans Change By: Michael Smith Affects Version/s: BOLT 0.6.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-190) Tasks in subfolders of a module are incorrectly loaded from plans
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-190 Tasks in subfolders of a module are incorrectly loaded from plans Change By: Michael Smith Fix Version/s: BOLT 0.6.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-190) Tasks in subfolders of a module are incorrectly loaded from plans
Title: Message Title Michael Smith commented on BOLT-190 Re: Tasks in subfolders of a module are incorrectly loaded from plans Loading tasks that live in subdirectories, such as sample/tasks/subdir/echo.sh worked in Bolt 0.4.1. It looks like by Bolt 0.6.0 that no longer worked. To maintain compatibility with PE, we believe the current behavior in Bolt 0.6.0+ is appropriate (until we intentionally add new features that add new semantics to tasks via directory structure). Plans behave differently in the current Bolt version: you can use subdirectories, so a plan at sample/plans/subdir/foo.pp named sample::subdir::foo can be invoked. As plans are Puppet code, this seems appropriate and doesn't impact PE or potential future features around task structure. I'll add tests around the current behavior, but I don't expect to add any functional changes. Closing as Won't Fix, as this is the current intended behavior. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-252) Run Bolt acceptance tests on merge
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-252 Run Bolt acceptance tests on merge Change By: Michael Smith Assignee: Zach Reichert Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-266 Log run_* actions when called from a plan Change By: Alex Dreyer Currently are no log messages at the default log level when a plan is run. As a first iteration in improving this problem we can add some log messages to run_* functions in bolt. It's likely that as we improve the output some of this logging will change but doing it now allows us to get quicker feedback. h2. ConstraintsLoggers will likely work the same for both run_task and run_plan. Since run_task prints a lot of information to stdout we need to avoid duplication. WARN prefacing normal messages may be concerning to users.h2. Current StateIn addition to the stdout stream we have 5 log levels to work with in bolt- DEBUG- INFO- WARN(default)- ERROR- FATAL(used before exiting)DEBUG:- log connection information- log every sub-action taken on a node like changing a task file permissions- log results from each action on a nodeINFO:- log whenever an action is started on nodeh2. Proposed changesThis involves adding a new log level notice and making it the default.DEBUG:- log when actions are started on nodes- log subactions- log connection information(This is controlled by net:ssh not us)INFO:- Log when actions start on nodes- Log the results of each action on each nodeNOTICE:- log when a run_* call is starting and what the first argument(command, script, task, or file) is- log when a run_* call finishes and summarize how many nodes succeeded or failedh2. Out of scope:- logging node failures by default. This would result in duplicate output or different logging inside the executor depending on what mode it was running in. It may make sense longer term as part of default output- specifying the warn log level on the commandline. It can be specified in the config file. We could also remove the --debug and --verbose CLI flags and replace them with --loglevel = error|warn|notice|info|debug Add Comment This message was sent by Atlassian JIRA
Jira (PDB-3796) memory leak in reports querying
Title: Message Title Wyatt Alt commented on PDB-3796 Re: memory leak in reports querying Russell Mull Erik Hansen this will probably be an issue for any large customer you ask for an export from. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-266 Log run_* actions when called from a plan Change By: Alex Dreyer Currently are no log messages at the default log level when a plan is run. As a first iteration in improving this problem we can add some log messages to run_* functions in bolt.h2. ConstraintsLoggers will likely work the same for both run_task and run_plan. Since run_task prints a lot of information to stdout we need to avoid duplication. WARN prefacing normal messages may be concerning to users.h2. Current StateIn addition to the stdout stream we have 5 log levels to work with in bolt- DEBUG- INFO- WARN(default)- ERROR- FATAL(used before exiting)DEBUG:- log connection information- log every sub-action taken on a node like changing a task file permissions- log results from each action on a nodeINFO:- log whenever an action is started on nodeh2. Proposed changesThis involves adding a new log level notice and making it the default.DEBUG:- log when actions are started on nodes- log subactions- log connection information(This is controlled by net:ssh not us)INFO:- Log when actions start on nodes- Log the results of each action on each nodeNOTICE:- log when a run_* call is starting and what the first argument(command, script, task, or file) is- log when a run_* call finishes and summarize how many nodes succeeded or failedh2. Out of scope:- logging node failures by default. This would result in duplicate output or different logging inside the executor depending on what mode it was running in. It may make sense longer term as part of default output- specifying the warn log level on the commandline. It can be specified in the config file. We could also remove the --debug and --verbose CLI flags and replace them with --loglevel = error|warn|notice|info|debug Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PDB-3796) memory leak in reports querying
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3796 memory leak in reports querying Issue Type: Bug Assignee: Unassigned Created: 2017/12/18 1:57 PM Priority: Normal Reporter: Wyatt Alt This presents like a recurrence of PDB-3467 . I don't know if that means Cheshire has regressed or if this is something new. I'm on a PuppetDB 5.1.1 build with full report data for about 10 hosts and a 512 mb heap (noticed the issue on a 256mb heap). If I query for all reports, results start streaming back but the server crashes before the response is complete. Add Comment
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-266 Log run_* actions when called from a plan Change By: Alex Dreyer Currently are no log messages at the default log level when a plan is run. As a first iteration in improving this problem we can add some log messages to run_* functions in bolt.h2. ConstraintsLoggers will likely work the same for both run_task and run_plan. Since run_task prints a lot of information to stdout we need to avoid duplication. WARN prefacing normal messages may be concerning to users.h2. Current StateIn addition to the stdout stream we have 5 log levels to work with in bolt- DEBUG- INFO- WARN(default)- ERROR- FATAL(used before exiting)DEBUG:- log connection information- log every sub-action taken on a node like changing a task file permissions- log results from each action on a nodeINFO:- log whenever an action is started on nodeh2. Proposed changesThis involves adding a new log level notice and making it the default.DEBUG:- log when actions are started on nodes- log subactions- log connection information(This is controlled by net:ssh not us)INFO:- Log when actions start on nodes- Log the results of each action on each nodeNOTICE:- log when a run_* call is starting and what the first argument(command, script, task, or file) is- log when a run_* call finishes and summarize how many nodes succeeded or failed h2. Out of scope:- logging node failures by default. This would result in different logging inside the executor depending on what mode it was running in. It may make sense longer term as part of default output- specifying the warn log level on the commandline. It can be specified in the config file. We could also remove the --debug and --verbose CLI flags and replace them with --loglevel = error|warn|notice|info|debug Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-266 Log run_* actions when called from a plan Change By: Alex Dreyer Currently are no log messages at the default log level when a plan is run. As a first iteration in improving this problem we can add some log messages to run_* functions in bolt. h3 h2 . Constraints : Loggers will likely work the same for both run_task and run_plan. Since run_task prints a lot of information to stdout we need to avoid duplication . WARN prefacing normal messages may be concerning to users. h3 h2 . Current StateIn addition to the stdout stream we have 5 log levels to work with in bolt- DEBUG- INFO- WARN(default)- ERROR- FATAL(used before exiting)DEBUG:- log connection information- log every sub-action taken on a node like changing a task file permissions- log results from each action on a nodeINFO:- log whenever an action is started on node h3 h2 . Proposed changes : This involves adding a new log level notice and making it the default.DEBUG:- log when actions are started on nodes- log subactions- log connection information(This is controlled by net:ssh not us)INFO:- Log when actions start on nodes- Log the results of each action on each nodeNOTICE:- log when a run_* call is starting and what the first argument(command, script, task, or file) is- log when a run_* call finishes and summarize how many nodes succeeded or failed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-266 Log run_* actions when called from a plan Change By: Alex Dreyer Currently are no log messages at the default log level when a plan is run. As a first iteration in improving this problem we can add some log messages to run_* functions in bolt. h3. Constraints:Loggers will likely work the same for both run_task and run_plan. Since run_task prints a lot of information to stdout we need to avoid duplicationWARN prefacing normal messages may be concerning to users.h3. Current StateIn addition to the stdout stream we have 5 log levels to work with in bolt- DEBUG- INFO- WARN(default)- ERROR- FATAL(used before exiting)DEBUG:- log connection information- log every sub-action taken on a node like changing a task file permissions- log results from each action on a nodeINFO:- log whenever an action is started on nodeh3. Proposed changes: This involves adding a new log level notice and making it the default.DEBUG:- log when actions are started on nodes- log subactions- log connection information(This is controlled by net:ssh not us)INFO:- Log when actions start on nodes- Log the results of each action on each nodeNOTICE:- log when a run_* call is starting and what the first argument(command, script, task, or file) is- log when a run_* call finishes and summarize how many nodes succeeded or failed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-266 Log run_* actions when called from a plan Change By: Alex Dreyer Currently are no log messages at the default log level when a plan is run. h3. Constraints: In addition to the stdout stream we have 5 log levels to work with in bolt- DEBUG- INFO- WARN(default)- ERROR- FATAL(used before exiting) Loggers will likely work the same for both run_task and run_plan. Since run_task prints a lot of information to stdout we need to avoid duplicationWARN prefacing normal messages may be concerning to users. h3. Current state: State In addition to the stdout stream we have 5 log levels to work with in bolt- DEBUG - INFO- WARN(default)- ERROR- FATAL(used before exiting)DEBUG :- log connection information- log every sub-action taken on a node like changing a task file permissions- log results from each action on a nodeINFO:- log whenever an action is started on node h3. Proposed changes: This involves adding a new log level notice and making it the default. DEBUG:- log when actions are started on nodes- log subactions- log connection information(This is controlled by net:ssh not us)INFO:- Log when actions start on nodes- Log the results of each action on each nodeNOTICE:- log when a run_* call is starting and what the first argument(command, script, task, or file) is- log when a run_* call finishes and summarize how many nodes succeeded or failed Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups
Jira (PUP-6739) Error running puppet with non-existent and non-default environment
Title: Message Title Eric Delaney commented on PUP-6739 Re: Error running puppet with non-existent and non-default environment Tested on SHA=85eed087b7c38e34d6d6465d94d016ab129268df SUITE_VERSION=5.3.3.140.g85eed08 PASSED [root@wmflkyw0qx7ablp ~]# puppet config print environment production [root@wmflkyw0qx7ablp ~]# puppet config set environment 'foo' Warning: The environment should be set in either the `[user]`, `[agent]`, or `[master]` section. Variables set in the `[agent]` section are used when running `puppet agent`. Variables set in the `[user]` section are used when running various other puppet subcommands, like `puppet apply` and `puppet module`; these require the defined environment directory to exist locally. Set the config section by using the `--section` flag. For example,
Jira (BOLT-263) log bolt results to a log file
Title: Message Title Alex Dreyer commented on BOLT-263 Re: log bolt results to a log file Currently we have two types of output we display to users with bolt which I will call logs and results. Logs go to stderr and results go to stdout. This is a pattern we use in other puppet tools(puppet, code-manager, r10k etc) because it allows us to build a CLI with a JSON output schema that is optimized for the general use case while still being flexible with other messages displayed to the user. We can print any message we want anywhere in the workflow as a log message and still have a single Result object that is more than a 'list of events' the user would have to sift through. Logs: These are prefixed by standard parsable fields and may be parseable by machines to some extent but are not considered a stable API. They can be generated anywhere in the code and adding new data is easy. Results: We have more flexibility with how these are displayed. The user controls how they are printed with the --format option. Adding new data is expensive because all formats need to be updated to handle it without breaking the current JSON schema One file per node sounds like a result database rather then a log file. Is there a ticket for that behavior other than BOLT-172? The one file per node behavior would fit into the current bolt as a result formatter called file or something. Would run plan append results to the node file or have different node files for each run_*? One file per bolt execution is just the current JSON formatter redirected to a file. If we wanted to make that built in behavior we would need to be able to generate a unique id for each bolt execution(job?) and save them to a directory. My understanding of the scope of this ticket is that it was limited to what we do with the "log" output. Getting that into a database like logstash would be left up to the user. If we're not happy with that or don't think it solves the user problem we'll have to step back and spend more time designing this ticket. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-3963) Error message gives wrong advice for allowed module names
Title: Message Title Kris Bosland updated an issue Puppet / PUP-3963 Error message gives wrong advice for allowed module names Manually checked that new error message appears properly. Change By: Kris Bosland QA Risk Assessment: Manual Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8223) User and group modifications should respect forcelocal
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-8223 User and group modifications should respect forcelocal Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8223) User and group modifications should respect forcelocal
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8223 User and group modifications should respect forcelocal Change By: Melissa Stone Sub-team: Coremunity Team: Platform Core Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3940) Puppet requests should include "real" MIME types
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3940 Puppet requests should include "real" MIME types Change By: Josh Cooper Fix Version/s: PUP 4.10.5 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-263) log bolt results to a log file
Title: Message Title
Jenny Mahmoudi commented on BOLT-263
Re: log bolt results to a log file
This is the primary job story I'm aware of:
When I run Bolt interactively, I want to view Bolt output in any format on the command line, but save the output to a log file in a machine-readable format (JSON or oneline) so that I can parse it later.
Why might it matter whether they need it for auditing later or immediate debugging? What would that change?
Separate question: can this be one file per bolt run?
The original spec called for 1 file per node, which was for technical reasons, not based on user needs, iirc: https://github.com/puppetlabs/bolt/blob/master/ux/bolt-CLI-spec.md {{--outputdir Specify a directory to save output logs (1 file per node).}}
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-155) Show list of available tasks with bolt task show
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-155 Show list of available tasks with bolt task show Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-266) Log run_* actions when called from a plan
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-266 Log run_* actions when called from a plan Issue Type: Improvement Assignee: Unassigned Created: 2017/12/18 12:09 PM Priority: Normal Reporter: Alex Dreyer Currently are no log messages at the default log level when a plan is run. Constraints: In addition to the stdout stream we have 5 log levels to work with in bolt DEBUG INFO WARN(default) ERROR FATAL(used before exiting) Loggers will likely work the same for both run_task and run_plan. Since run_task prints a lot of information to stdout we need to avoid duplication WARN prefacing normal messages may be concerning to users. Current state: DEBUG: log connection information
Jira (BOLT-155) Show list of available tasks with bolt task show
Title: Message Title Michael Smith commented on BOLT-155 Re: Show list of available tasks with bolt task show Ok, I was concerned about performance of that. Presumably it caches files loaded during list_tasks? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8131) Calls to Puppet::Util.benchmark should include a 'in %{seconds} seconds' in there message
Title: Message Title
Melissa Stone updated an issue
Puppet / PUP-8131
Calls to Puppet::Util.benchmark should include a 'in %{seconds} seconds' in there message
Change By:
Melissa Stone
Fix Version/s:
PUP 5.3.4
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8131) Calls to Puppet::Util.benchmark should include a 'in %{seconds} seconds' in there message
Title: Message Title
Melissa Stone commented on PUP-8131
Re: Calls to Puppet::Util.benchmark should include a 'in %{seconds} seconds' in there message
Merged into 5.3.x at https://github.com/puppetlabs/puppet/commit/fa13f1a10b718105e98ad2fe523d5bf0fc688e73
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8256) automatically removing my cert after generating it
Title: Message Title Josh Cooper commented on PUP-8256 Re: automatically removing my cert after generating it It looks like you have autosigning enabled, so puppet is immediately signing the CSR as soon as it is received: Notice: Signed certificate request for slavepoc.edc If you want to control the signing process, then turn off autosigning. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8255) gem package provider broken with Rubygems 2.7.x
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8255 gem package provider broken with Rubygems 2.7.x Change By: Jacob Helwig Sub-team: Coremunity Team: Platform Core Sprint: Platform Core Grooming Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8122) I18n strings that include repeated lists of sentence fragments can be hard to translate
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8122
I18n strings that include repeated lists of sentence fragments can be hard to translate
Change By:
Eric Delaney
We need to review the PO file and source code of pupppet puppet looking for strings where we build up a list of things where we include sentence fragment in the repeated list and determine if this should be change to allow for better translationsFor example the below code includes a sentence fragment "which depends on" which will be hard to translate into Japanese, We should create a list of cases, review them and determine which ones we want to change string in.lib/puppet/module_tool/errors/shared.rb{code}_("which depends on '%{name}' (%{version})") % { name: m[:name], version: v(m[:version]) }{code}{code} dependency_list = @source[1..-1].map do |m|#TRANSLATORS This message repeats as separate lines as a list under the heading "You specified '%{name}' (%{version})\n"_("which depends on '%{name}' (%{version})") % { name: m[:name], version: v(m[:version]) } end.join(",\n") msg_variables = { requested_module: @requested_module, version: v(@requested_version), module_name: @module_name,name: @source.first[:name], dependency_list: dependency_list } _(<<-EOM).chomp % msg_variablesCould not install module '%{requested_module}' (%{version}) No version of '%{module_name}' will satisfy dependenciesYou specified '%{name}' (%{version})%{dependency_list}Use `puppet module install --force` to install this module anyway EOM{code} {code}_("You may have meant `puppet module %{action} %{suggestion}`") % { action: @action, suggestion: suggestion }{code}{code} suggestion_list = @suggestions.map do |suggestion|_("You may have meant `puppet module %{action} %{suggestion}`") % { action: @action, suggestion: suggestion } end.join("\n") if @action == :upgrade# TRANSLATORS `puppet module install` is a command line and We should not be translated_(<<-EOM).chomp % { action: @action, module_name: @module_name, suggestion_list: suggestion_list }Could not %{action} module '%{module_name}' Module '%{module_name}' is not installed%{suggestion_list}Use `puppet module install` look to install this moduleEOM else_(<<-EOM).chomp % { action: @action, module_name: @module_name, suggestion_list: suggestion_list }Could not %{action} module '%{module_name}' Module '%{module_name}' is not installed%{suggestion_list}EOM end{code}{code}_("'%{module_name}' (%{version}) was found in %{path}") % { module_name: @module_name, version: v(mod.version), path: mod.modulepath }{code}{code} module_path_list = @modules.map do |mod|#TRANSLATORS This is repeats as separate lines as a list under "Module '%{module_name}' appears multiple places in update the module path"_("'%{module_name}' (%{version}) was found in %{path}") % { module_name: @module_name, version: v(mod.version), path: mod.modulepath } end.join("\n") # TRANSLATORS `--modulepath` is command line option and should not repeated list text to be translated _ ( <<-EOM and remove the TRANSLATOR comment ) .chomp % { action: @action, module_name:
Jira (PUP-8122) I18n strings that include repeated lists of sentence fragments can be hard to translate
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8122 I18n strings that include repeated lists of sentence fragments can be hard to translate Change By: Eric Delaney Sprint: Platform Core Grooming Hopper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8122) I18n strings that include repeated lists of sentence fragments can be hard to translate
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8122 I18n strings that include repeated lists of sentence fragments can be hard to translate Change By: Eric Delaney Comment: Since we're moving away from Here docs for these translated strings, this problem is addressed. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7630) "Successful" puppet agent reports hide provider errors
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7630 "Successful" puppet agent reports hide provider errors Change By: Craig Gomes Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8106) "mount" type should autorequire its mountpoint
Title: Message Title Josh Cooper assigned an issue to Kris Bosland Puppet / PUP-8106 "mount" type should autorequire its mountpoint Change By: Josh Cooper Assignee: Kris Bosland Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8131) Calls to Puppet::Util.benchmark should include a 'in %{seconds} seconds' in there message
Title: Message Title
Josh Cooper assigned an issue to Melissa Stone
Puppet / PUP-8131
Calls to Puppet::Util.benchmark should include a 'in %{seconds} seconds' in there message
Change By:
Josh Cooper
Assignee:
Eric Delaney Melissa Stone
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8244) Enable Lint/UselessAssignment rubocop check
Title: Message Title Josh Cooper assigned an issue to Jacob Helwig Puppet / PUP-8244 Enable Lint/UselessAssignment rubocop check Change By: Josh Cooper Assignee: Josh Cooper Jacob Helwig Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3963) Error message gives wrong advice for allowed module names
Title: Message Title Josh Cooper assigned an issue to Kris Bosland Puppet / PUP-3963 Error message gives wrong advice for allowed module names Change By: Josh Cooper Assignee: Kris Amundson Bosland Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3963) Error message gives wrong advice for allowed module names
Title: Message Title Josh Cooper assigned an issue to Kris Amundson Puppet / PUP-3963 Error message gives wrong advice for allowed module names Change By: Josh Cooper Assignee: Kris Amundson Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6739) Error running puppet with non-existent and non-default environment
Title: Message Title Josh Cooper assigned an issue to Eric Delaney Puppet / PUP-6739 Error running puppet with non-existent and non-default environment Change By: Josh Cooper Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8262) Non-existent Solaris SMF services are no longer defined as :stopped (LTS breaking change)
Title: Message Title Scott Garman updated an issue Puppet / PUP-8262 Non-existent Solaris SMF services are no longer defined as :stopped (LTS breaking change) Change By: Scott Garman Release Notes Summary: In Puppet 4.10.9, non-existent Solaris SMF services reported a state of :absent instead of :stopped. This change could break some workflows, so the behavior has been reverted in this release to report non-existent Solaris SMF services as :stopped. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8262) Non-existent Solaris SMF services are no longer defined as :stopped (LTS breaking change)
Title: Message Title Scott Garman updated an issue Puppet / PUP-8262 Non-existent Solaris SMF services are no longer defined as :stopped (LTS breaking change) Change By: Scott Garman Fix Version/s: PUP 4.10.10 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8262) Non-existent Solaris SMF services are no longer defined as :stopped (LTS breaking change)
Title: Message Title Scott Garman created an issue Puppet / PUP-8262 Non-existent Solaris SMF services are no longer defined as :stopped (LTS breaking change) Issue Type: Bug Assignee: Unassigned Created: 2017/12/18 9:11 AM Priority: Normal Reporter: Scott Garman In Puppet 4.10.9, the behavior of non-existent Solaris SMF services changed, and at least one PE customer with a large Solaris install base has reported that this is preventing them from upgrading within the LTS series. Previously, non-existent Solaris SMF services reported their state as :stopped, and could be defined as :stopped in Puppet code, to ensure that unwanted services were not running, even if they were not installed. In Puppet 4.10.9, this behavior was changed to cause non-existent Solaris SMF services to report a state of :absent. A change like this should probably not be included in our LTS releases. Reverting the commits related to this change should be sufficient to resolve this issue for our customers. Add Comment
Jira (PUP-8262) Non-existent Solaris SMF services are no longer defined as :stopped (LTS breaking change)
Title: Message Title Scott Garman assigned an issue to Scott Garman Puppet / PUP-8262 Non-existent Solaris SMF services are no longer defined as :stopped (LTS breaking change) Change By: Scott Garman Assignee: Scott Garman Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8261) Restore refactored Solaris SMF acceptance tests to consolidate them
Title: Message Title Scott Garman updated an issue Puppet / PUP-8261 Restore refactored Solaris SMF acceptance tests to consolidate them Change By: Scott Garman In the process of fixing PE-22951, we've had to revert a bunch of code related to the Solaris SMF provider, including a commit which consolidated the SMF acceptance tests for efficiency:https://github.com/puppetlabs/puppet/commit/b539fe581f372514e28f4c7e095d81dc8b0f500cOnce PE-22951 is fixed, this ticket is to track the work of re-consolidating those SMF tests that were split up again by when reverting the above commit. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8261) Restore refactored Solaris SMF acceptance tests to consolidate them
Title: Message Title Scott Garman created an issue Puppet / PUP-8261 Restore refactored Solaris SMF acceptance tests to consolidate them Issue Type: Improvement Assignee: Scott Garman Created: 2017/12/18 8:59 AM Priority: Normal Reporter: Scott Garman In the process of fixing PE-22951, we've had to revert a bunch of code related to the Solaris SMF provider, including a commit which consolidated the SMF acceptance tests for efficiency: https://github.com/puppetlabs/puppet/commit/b539fe581f372514e28f4c7e095d81dc8b0f500c Once PE-22951 is fixed, this ticket is to track the work of re-consolidating those SMF tests that were split up again by reverting the above commit. Add Comment This
Jira (BOLT-261) Uppercase class task name should not work as a reference to a task in a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-261 Uppercase class task name should not work as a reference to a task in a plan Change By: Alex Dreyer Summary: Quoted Uppercase class task name should not work as a reference to a task in a plan Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-252) Run Bolt acceptance tests on merge
Title: Message Title Zach Reichert assigned an issue to Zach Reichert Puppet Task Runner / BOLT-252 Run Bolt acceptance tests on merge Change By: Zach Reichert Assignee: Nick Lewis Zach Reichert Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-261) Quoted class task name should not work as a reference to a task in a plan
Title: Message Title Zach Reichert commented on BOLT-261 Re: Quoted class task name should not work as a reference to a task in a plan We currently enforce lower_snake_case for task names. https://puppet.com/docs/bolt/0.x/writing_tasks.html#naming-tasks At least in PE. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8259) PAL list_tasks doesn't display file information when parsing error is encountered
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-8259 PAL list_tasks doesn't display file information when parsing error is encountered Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8260) Using eval_generate with a compound name_vars without a name appears to not work
Title: Message Title
Glenn Sarti updated an issue
Puppet / PUP-8260
Using eval_generate with a compound name_vars without a name appears to not work
Change By:
Glenn Sarti
I have a custom type called registry_key with an eval_generate method which can purge values. The resource types created by eval_generate are {{registry_value}} which is now a type with compound namevars. When creating an instance of the type, it is required to pass a title ( compound namevar types appear to need _something_ simple as a resource key . ) This is fine and all works ok however in a proper puppet run the generated resources do not appear in the catalog correctly.I've tracked it down to:https://github.com/puppetlabs/puppet/blob/master/lib/puppet/transaction/additional_resource_generator.rb#L66{code} made = Hash[generated.map(&:name).zip(generated)]{code}It appears that this code takes each resources :name method and does "something" with it. The issue becomes that the compound namevar types return `nil` for it's name which then screws up the catalog.After digging into the Puppet::Type type I found a commit (https://github.com/puppetlabs/puppet/commit/607d7c6afec7ab73203382676cc98b6d52898e1d) from Luke back in 2006 which was converting the Puppet::Type name method into title. It appears that additional_resource_generator.rb was never updated to reflect this.Also there are quotes in the code from that commit{code}+# For now, leave the 'name' method functioning like it used to. Once 'title'+# works everywhere, I'll switch it.{code}Currently:https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type.rb#L2535-L2543Would it be safe to switch it now after 12 years?
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8260) Using eval_generate with a compound name_vars without a name appears to not work
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-8260 Using eval_generate with a compound name_vars without a name appears to not work Change By: Glenn Sarti Team: Windows Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8260) Using eval_generate with a compound name_vars without a name appears to not work
Title: Message Title Glenn Sarti assigned an issue to Unassigned Puppet / PUP-8260 Using eval_generate with a compound name_vars without a name appears to not work Change By: Glenn Sarti Assignee: Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8260) Using eval_generate with a compound name_vars without a name appears to not work
Title: Message Title Glenn Sarti commented on PUP-8260 Re: Using eval_generate with a compound name_vars without a name appears to not work Removing from Windows team to Puppet Agent Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8260) Using eval_generate with a compound name_vars without a name appears to not work
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-8260 Using eval_generate with a compound name_vars without a name appears to not work Change By: Glenn Sarti Sprint: Windows Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8260) Using eval_generate with a compound name_vars without a name appears to not work
Title: Message Title Glenn Sarti commented on PUP-8260 Re: Using eval_generate with a compound name_vars without a name appears to not work I've created a minimal repro module Source - https://github.com/glennsarti/PUP8260-repro PUP8260-repro-master.zip There are three tests cases, and in each case: A single "parent" resource exists which will purge any unmanaged children Two "child" resources exist (called `managed1` and `managed2`) which will autorequire the "parent" There will appear to be four children that exist for the parent (called `managed1`, `managed2`, `unmanaged1`, and `unmanaged2`) thus it should try to purge the unmanaged entries (called `unmanaged1` and `unmanaged2`) The providers for both the "child" and "parent" are just stubs which write to STDOUT for its various actions e.g. Create, Destroy and Flush See the README for more information - https://github.com/glennsarti/PUP8260-repro/blob/master/README.md Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed
Jira (PUP-8260) Using eval_generate with a compound name_vars without a name appears to not work
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-8260 Using eval_generate with a compound name_vars without a name appears to not work Change By: Glenn Sarti Attachment: PUP8260-repro-master.zip Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
