Jira (PUP-4242) Add deprecation warnings for manifests declaring things in wrong namespace
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4242 Add deprecation warnings for manifests declaring things in wrong namespace Change By: Josh Cooper Fix Version/s: PUP 5.5.2 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-4242) Add deprecation warnings for manifests declaring things in wrong namespace
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4242 Add deprecation warnings for manifests declaring things in wrong namespace Change By: Josh Cooper Fix Version/s: PUP 5.y Fix Version/s: PUP 5.5.2 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-8568) Extract cron type/provider into a module
Title: Message Title Jennifer Solman assigned an issue to Unassigned Puppet / PUP-8568 Extract cron type/provider into a module Change By: Jennifer Solman Assignee: Jennifer Solman 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-8568) Extract cron type/provider into a module
Title: Message Title Jennifer Solman commented on PUP-8568 Re: Extract cron type/provider into a module If you would like to continue on with the work that was already started: https://github.com/8675309/puppetlabs-cron_core Initial PDK validate corrections were performed. Next step: First acceptance test in: should_allow_changing_parameters_spec.rb is passing (thanks Eric Putnam!). Use this to get the rest of the tests in that file to pass, and continue with the rest of the acceptance test files 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-533) Move facts to an external module
Title: Message Title Michael Smith commented on BOLT-533 Re: Move facts to an external module I'm not sure this is worth working on until we decide whether we'll rename facter_task. We'll want to hold off releasing anything until we do, and doing something we don't have a plan for releasing seems like a waste. 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-545) upload/script/task don't work with --run-as on AIX (and possibly others)
Title: Message Title Michael Smith commented on BOLT-545 Re: upload/script/task don't work with --run-as on AIX (and possibly others) Apparently some platforms don't support id -g. On Solaris 10 at least, you need to use /usr/xpg4/bin/id -g. I'm ok not supporting Solaris 10 right now. 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-545) upload/script/task don't work with --run-as on AIX (and possibly others)
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-545 upload/script/task don't work with --run-as on AIX (and possibly others) Change By: Michael Smith Sprint: Bolt Kanban 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-8767) --config_version option to `puppet apply` leads to ruby-specific lastrun YAML
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8767 --config_version option to `puppet apply` leads to ruby-specific lastrun YAML Change By: Josh Cooper Fix Version/s: PUP 5.5.3 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-8767) --config_version option to `puppet apply` leads to ruby-specific lastrun YAML
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8767 --config_version option to `puppet apply` leads to ruby-specific lastrun YAML Change By: Josh Cooper Team: 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-8767) --config_version option to `puppet apply` leads to ruby-specific lastrun YAML
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8767
--config_version option to `puppet apply` leads to ruby-specific lastrun YAML
Change By:
Josh Cooper
If you run {{ puppet apply -- custom_version config_version ='echo foo' -e 'notify \{ "bar": \}'}} then the last run summary YAML ends up looking like this{noformat}---version: config: !ruby/string:Puppet::Util::Execution::ProcessOutput "foo"[...]{noformat}Having the explicit typing makes it difficult to parse with general YAML tools.
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-545) upload/script/task don't work with --run-as on AIX (and possibly others)
Title: Message Title Michael Smith commented on BOLT-545 Re: upload/script/task don't work with --run-as on AIX (and possibly others) We should update the chown commands to use an explicit user:group for portability. Group can be queried via id -g user. 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-545) upload/script/task don't work with --run-as on AIX (and possibly others)
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-545 upload/script/task don't work with --run-as on AIX (and possibly others) Issue Type: Bug Assignee: Unassigned Created: 2018/05/25 11:16 AM Priority: Normal Reporter: Nick Lewis When we need to change the owner of a file over SSH (which we do when using run-as while uploading files, running scripts or running tasks), we do so with chown username: file. The trailing colon means "set the group of the file to the primary group of the user". However, that syntax isn't universally supported (AIX in particular). That causes the run to fail. We need to come up with some alternative solution for setting group on those platforms. Add Comment
Jira (BOLT-544) PuppetDB integration should work out-of-the-box with PE
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-544 PuppetDB integration should work out-of-the-box with PE Change By: Cas Donoghue Assignee: Cas Donoghue 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-544) PuppetDB integration should work out-of-the-box with PE
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-544 PuppetDB integration should work out-of-the-box with PE Change By: Cas Donoghue Sprint: Bolt Kanban 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-8578) Extract sshkeys type/provider into a module
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8578 Extract sshkeys type/provider into a module Change By: Jacob Helwig Sprint: Platform Core Hopper KANBAN 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-494) Document how to opt-out of analytics
Title: Message Title David Kramer commented on BOLT-494 Re: Document how to opt-out of analytics We could document the collection of analytics on our primary product page; this has brief installation instructions, with a link to more detailed instructions: https://puppet.com/products/puppet-bolt The more detailed instructions are here: https://puppet.com/docs/bolt/0.x/bolt_installing.html We could also document the collection of analytics on our project page: https://github.com/puppetlabs/bolt Is one of these places the "best" place? Do we need to include the message in all three locations to be safe? 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-8578) Extract sshkeys type/provider into a module
Title: Message Title Jacob Helwig assigned an issue to Jacob Helwig Puppet / PUP-8578 Extract sshkeys type/provider into a module Change By: Jacob Helwig Assignee: Jacob Helwig 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-544) PuppetDB integration should work out-of-the-box with PE
Title: Message Title
Cas Donoghue created an issue
Puppet Task Runner / BOLT-544
PuppetDB integration should work out-of-the-box with PE
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2018/05/25 10:58 AM
Priority:
Normal
Reporter:
Cas Donoghue
Configuration details for puppetdb connection should be loaded from: a) bolt config b) ~/.puppetlabs/client-tools/puppetdb.conf c) /etc/puppetlabs/client-tools/puppetdb.conf [path is platform-dependent] Currently with default PE install:
$ bolt command run hostname --query 'nodes[certname] {}'
server_urls must be specified
Bolt should attempt to find db connection info in puppetdb.conf when puppetdb is not defined in configfile.
Jira (PUP-8768) Ability to export puppet Task output to CSV/Text file.
Title: Message Title Michael Smith commented on PUP-8768 Re: Ability to export puppet Task output to CSV/Text file. Can you be a little clearer about what you mean by a puppet task run? Is that specifically using the puppet task run command? If so, then you can add --format json to get structured output. If Bolt, you have a similar option. 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-8768) Ability to export puppet Task output to CSV/Text file.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8768 Ability to export puppet Task output to CSV/Text file. Change By: Josh Cooper Team: Direct Change 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-8768) Ability to export puppet Task output to CSV/Text file.
Title: Message Title Josh Cooper commented on PUP-8768 Re: Ability to export puppet Task output to CSV/Text file. ping Alex Dreyer 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-8772) Using --confdir doesn't redirect other default directories
Title: Message Title Josh Cooper commented on PUP-8772 Re: Using --confdir doesn't redirect other default directories This is expected, though I understand it's a little awkward on Windows as everything is within a common prefix C:/ProgramData/PuppetLabs. In puppet there are 5 "root" directories and all settings are derived from them. If you only set conf dir, then the others will use the default locations. 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-8773) Logging as JSON broken
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8773 Logging as JSON broken Change By: Josh Cooper Fix Version/s: PUP 5.5.z Fix Version/s: PUP 5.5.3 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-8773) Logging as JSON broken
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8773 Logging as JSON broken Change By: Josh Cooper Team: 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-8890) 5.5 docs missing schema files
Title: Message Title Garrett Guillotte commented on PUP-8890 Re: 5.5 docs missing schema files Moving to the WEB project because I suspect this is a Drupal issue. The file_metadata.json file is present in the GitHub repo (puppetlabs/puppet-docs, /source/puppet/5.5/schemas/file_metadata.json) and being pushed to the shared storage for publishing to puppet.com/docs. CC Mike Prasuhn 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-519) Bolt should send a Bolt user agent header to orchestrator
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-519 Bolt should send a Bolt user agent header to orchestrator 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 (PDB-3927) Examine terminus for possible improvements once Ruby 1.9.3 support is dropped
Title: Message Title Rob Browning moved an issue PuppetDB / PDB-3927 Examine terminus for possible improvements once Ruby 1.9.3 support is dropped Change By: Rob Browning Key: PUP PDB - 8891 3927 Project: Puppet PuppetDB 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-8891) Examine terminus for possible improvements once Ruby 1.9.3 support is dropped
Title: Message Title Rob Browning created an issue Puppet / PUP-8891 Examine terminus for possible improvements once Ruby 1.9.3 support is dropped Issue Type: Improvement Assignee: Unassigned Created: 2018/05/25 9:49 AM Priority: Normal Reporter: Rob Browning 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
Jira (PUP-8609) Bump FFI gem to ~> 1.9.22 to support Ruby 2.5
Title: Message Title Sean McDonald updated an issue Puppet / PUP-8609 Bump FFI gem to ~> 1.9.22 to support Ruby 2.5 Change By: Sean McDonald Team: Platform Core OS 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-543) Automate updating the version and sha of brew package
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-543 Automate updating the version and sha of brew package Issue Type: Improvement Assignee: Unassigned Created: 2018/05/25 9:33 AM Priority: Normal Reporter: Lucy Wyman The current bolt brew package lives at https://github.com/Homebrew/homebrew-cask/blob/master/Casks/puppet-bolt.rb, and has version set to 'latest' and is set to not check the sha. This is fine for now, but eventually we'll want to have the specific version and sha in that file. This means the new workflow will be to update that file and create a PR against https://github.com/Homebrew/homebrew-cask, which we want to be an automated part of our CI release pipeline. This automation should be generalized so the pdk team can also take advantage of it. Add Comment
Jira (PUP-8563) The puppet agent should have a 'local' mode for CRL checking
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8563 The puppet agent should have a 'local' mode for CRL checking Change By: Maggie Dreyer Method Found: Needs Assessment Customer Feedback 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-8563) The puppet agent should have a 'local' mode for CRL checking
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8563 The puppet agent should have a 'local' mode for CRL checking Change By: Maggie Dreyer Team: Coremunity Server 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-8563) The puppet agent should have a 'local' mode for CRL checking
Title: Message Title Maggie Dreyer commented on PUP-8563 Re: The puppet agent should have a 'local' mode for CRL checking I need to verify, but I think the docs may be unclear here. If Puppet detects that it has a CRL file on disk, it will not try to download one, regardless of the value of certificate_revocation. However, this could have implications for SERVER-2174, because in the intermediate CA case, we either need to know how to perform the modified check against the external CA, or we need to be able to disable updating the CRL. 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-8213) Error message for certificate name mismatch is clear as mud
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8213 Error message for certificate name mismatch is clear as mud Change By: Maggie Dreyer Sub-team: 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-8213) Error message for certificate name mismatch is clear as mud
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8213 Error message for certificate name mismatch is clear as mud Change By: Maggie Dreyer 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-8213) Error message for certificate name mismatch is clear as mud
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8213 Error message for certificate name mismatch is clear as mud Change By: Maggie Dreyer Team: Platform Core Server 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-4975) caching server certificate performed twice?
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-4975 caching server certificate performed twice? Change By: Maggie Dreyer 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-1935) puppetd ignores local ca.pem when connecting to master for the first time
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-1935 puppetd ignores local ca.pem when connecting to master for the first time Change By: Maggie Dreyer 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-1935) puppetd ignores local ca.pem when connecting to master for the first time
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-1935 puppetd ignores local ca.pem when connecting to master for the first time Change By: Maggie Dreyer Team: Platform Core Server 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-1935) puppetd ignores local ca.pem when connecting to master for the first time
Title: Message Title Maggie Dreyer assigned an issue to Unassigned Puppet / PUP-1935 puppetd ignores local ca.pem when connecting to master for the first time Change By: Maggie Dreyer Assignee: Jayant Sane 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-1935) puppetd ignores local ca.pem when connecting to master for the first time
Title: Message Title Maggie Dreyer commented on PUP-1935 Re: puppetd ignores local ca.pem when connecting to master for the first time As we are adding our new agent-side certificate code in place, with the new HTTP client, we should verify that this gets fixed. 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-7295) Puppet is too permissive about skipping SSL verification
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7295 Puppet is too permissive about skipping SSL verification Change By: Maggie Dreyer Team: Platform Core Server 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-7295) Puppet is too permissive about skipping SSL verification
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7295 Puppet is too permissive about skipping SSL verification Change By: Maggie Dreyer Sub-team: 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 (PDB-3357) PuppetDB fails to update catalogs when rich data types are enabled
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3357 PuppetDB fails to update catalogs when rich data types are enabled Change By: Rob Browning Team: Data Platform 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-8725) Agent Functions - Check Puppet Type Specifications against PDB
Title: Message Title Rob Browning commented on PUP-8725 Re: Agent Functions - Check Puppet Type Specifications against PDB The type definitions are here: https://github.com/puppetlabs/puppet-specifications/blob/master/language/types_values_variables.md 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-8887) puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Title: Message Title Henrik Lindberg assigned an issue to Stefan Andres Puppet / PUP-8887 puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml Change By: Henrik Lindberg Assignee: Henrik Lindberg Stefan Andres 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-8887) puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml
Title: Message Title Henrik Lindberg commented on PUP-8887 Re: puppet-5.5.0 breaks lookup_options when used post-loading dynamic items from hiera.yaml Looked at this again. I think the issue is that the feature convert_to requires getting the lookup options and doing that changes at what time the lookup options gets bound. Don't think that will change by reverting the commit in question. The fact remains that it is a really bad idea to have the hiera.config depend on the data it references. It is not designed to handle that. The input to the hiera.config is using must to come from facts, an ENC or from variables set in topscope in site.pp. The variables in top scope that the hiera config makes use of should not be set via a call to lookup as that makes the definition recursive/ambiguous. To make sure that the problem I describe in this comment is what is what is causing the problem - a quick test is to assign the $roles statically in site.pp and observe how that works. 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-4287) scheduled_task type doesn't support comment/description field
Title: Message Title Ethan Brown updated an issue Puppet / PUP-4287 scheduled_task type doesn't support comment/description field Change By: Ethan Brown The current scheduled_task type and provider doesn't support managing the comment field. (In the GUI this is calls Comments on Windows 2003 and Description on higher Windows releases, but let's call it comment as in the API).The methods for managing the comment are already in the provider and adding support to it is trivial. This is provided through the IRegistrationInfo interface - https://msdn.microsoft.com/en-us/library/windows/desktop/aa380773(v=vs.85).aspx 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 (BOLT-464) Publish Bolt to chocolatey.org
Title: Message Title Glenn Sarti commented on BOLT-464 Re: Publish Bolt to chocolatey.org Cuirrently in moderation queue https://chocolatey.org/packages/puppet-bolt/0.20.3 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.
