Jira (BOLT-191) Ability to upload directories or recursively upload files in plans
Title: Message Title Stephen Gelman commented on BOLT-191 Re: Ability to upload directories or recursively upload files in plans I tested this and as far as I can tell there's no downside to setting ":recursive => true" on the file upload. I still need to finish up writing tests for this but would anyone object to my finishing that then PRing it? 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-8920) puppet device does not support --target for CSR
Title: Message Title Rick Sherman commented on PUP-8920 Re: puppet device does not support --target for CSR More like user error. 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-8920) puppet device does not support --target for CSR
Title: Message Title Rick Sherman created an issue Puppet / PUP-8920 puppet device does not support --target for CSR Issue Type: Bug Assignee: Unassigned Created: 2018/06/08 5:16 PM Priority: Normal Reporter: Rick Sherman When attempting to limit the scope of a `puppet device` cert request, it cannot be limited to a single target We should either fix or document this. [root@puppet ~]# puppet device -v -t csr1kv -w 10 Error: Target device / certificate 'csr1kv' not found in /etc/puppetlabs/puppet/device.conf Add Comment
Jira (BOLT-559) Create rake task to generate reference documentation
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-559 Create rake task to generate reference documentation Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-559) Create rake task to generate reference documentation
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-559 Create rake task to generate reference documentation Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-559) Create rake task to generate reference documentation
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-559 Create rake task to generate reference documentation Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-559) Create rake task to generate reference documentation
Title: Message Title Michael Smith commented on BOLT-559 Re: Create rake task to generate reference documentation Started on this with a Rake task: https://github.com/MikaelSmith/bolt/tree/BOLT-559. However puppet strings generate --format json doesn't seem to work. Someone will need to dig into that. 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 (PDOC-207) i18n in puppet-strings
Title: Message Title
Eric Putnam updated an issue
Puppet Strings / PDOC-207
i18n in puppet-strings
Change By:
Eric Putnam
See PDOC-193 for info on existing yard tool.You can see this in raw action by simply calling the CLI tool from the PuppetStrings.generate method and then running strings on a module.{code:ruby}YARD::CLI::I18n.run(search_patterns){code}See from the attached file, there's a lot of stuff that we won't want in there. It will be confusing to the translator and lots of unnecessary work. A few examples:A lot of tags get the tag itself extracted into a msgid that looks like the one here:{code}# @param [String]#: ../lib/puppet/type/radius.rb:3#: ../manifests/install.pp:10msgid "tag|param|name"msgstr ""{code}First of all, we don't want the param name translated. Second, that's just confusing to look at.In other cases, we _do_ want part of this msgid. This mostly occurs in examples:{code}# @example#: ../lib/puppet/type/radius.rb:3msgid "tag|example|Here's an example"msgstr ""{code}Finally, we don't want to translate code examples, obviously{code} # @example Using the type.#: ../lib/puppet/type/test.rb:3msgid "test { 'mctesterson':\n"" foo => 'hi',\n"" my_prop => 'bar',\n""}"msgstr ""{code} The attached file also includes the README, which we may or may not want to pursue.So *this work probably involves*1. Running the #run method as suggested above2. Some kind of post-processing? I actually don't have a good idea. Monkey patching?
Add Comment
This message was sent by Atlassian JIRA
Jira (BOLT-559) Create rake task to generate reference documentation
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-559 Create rake task to generate reference documentation 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 (PDOC-207) i18n in puppet-strings
Title: Message Title
Eric Putnam updated an issue
Puppet Strings / PDOC-207
i18n in puppet-strings
Change By:
Eric Putnam
See PDOC-193 for info on existing yard tool.You can see this in raw action by simply calling the CLI tool from the PuppetStrings.generate method and then running strings on a module.{code:ruby}YARD::CLI::I18n.run(search_patterns){code} You can see See from the attached file, there's a lot of stuff that we won't want in there. It will be confusing to the translator and lots of unnecessary work. A few examples:A lot of tags get the tag itself extracted into a msgid that looks like the one here:{code}# @param [String]#: ../lib/puppet/type/radius.rb:3#: ../manifests/install.pp:10msgid "tag|param|name"msgstr ""{code}First of all, we don't want the param name translated. Second, that's just confusing to look at.In other cases, we _do_ want part of this msgid. This mostly occurs in examples:{code}# @example#: ../lib/puppet/type/radius.rb:3msgid "tag|example|Here's an example"msgstr ""{code}Finally, we don't want to translate code examples, obviously{code} # @example Using the type.#: ../lib/puppet/type/test.rb:3msgid "test { 'mctesterson':\n"" foo => 'hi',\n"" my_prop => 'bar',\n""}"msgstr ""{code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDOC-193) Evaluate using `yard i18n` to extract doc string content into POT files
Title: Message Title
Eric Putnam updated an issue
Puppet Strings / PDOC-193
Evaluate using `yard i18n` to extract doc string content into POT files
Change By:
Eric Putnam
Since 0.8.0 yard has included an {{i18n}} subcommand to place all the doc strings into a .pot file. It seems like if we just run this automatically when a user invokes {{puppet strings}} that would go a long way to enabling i18n workflows for module documentation. You can see this in raw action by simply calling the CLI tool from the PuppetStrings.generate method and then running strings on a module.{code:ruby}YARD::CLI::I18n.run(search_patterns){code}You can see from the attached file, there's a lot of stuff that we won't want in there. It will be confusing to the translator and lots of unnecessary work. A few examples:A lot of tags get the tag itself extracted into a msgid that looks like the one here:{code}# @param [String]#: ../lib/puppet/type/radius.rb:3#: ../manifests/install.pp:10msgid "tag|param|name"msgstr ""{code}First of all, we don't want the param name translated. Second, that's just confusing to look at.In other cases, we _do_ want part of this msgid. This mostly occurs in examples:{code}# @example#: ../lib/puppet/type/radius.rb:3msgid "tag|example|Here's an example"msgstr ""{code}Finally, we don't want to translate code examples, obviously{code} # @example Using the type.#: ../lib/puppet/type/test.rb:3msgid "test { 'mctesterson':\n"" foo => 'hi',\n"" my_prop => 'bar',\n""}"msgstr ""{code}
Add Comment
This message was sent by
Jira (PDOC-193) Evaluate using `yard i18n` to extract doc string content into POT files
Title: Message Title
Eric Putnam updated an issue
Puppet Strings / PDOC-193
Evaluate using `yard i18n` to extract doc string content into POT files
Change By:
Eric Putnam
Since 0.8.0 yard has included an {{i18n}} subcommand to place all the doc strings into a .pot file. It seems like if we just run this automatically when a user invokes {{puppet strings}} that would go a long way to enabling i18n workflows for module documentation.You can see this in raw action by simply calling the CLI tool from the PuppetStrings.generate method and then running strings on a module.{code:ruby}YARD::CLI::I18n.run(search_patterns){code} You can see from the attached file, there's a lot of stuff that we won't want in there. It will be confusing to the translator and lots of unnecessary work. A few examples:A lot of tags get the tag itself extracted into a msgid that looks like the one here:{code}# @param [String]#: ../lib/puppet/type/radius.rb:3#: ../manifests/install.pp:10msgid "tag|param|name"msgstr ""{code}First of all, we don't want the param name translated. Second, that's just confusing to look at.In other cases, we _do_ want part of this msgid. This mostly occurs in examples:{code}# @example#: ../lib/puppet/type/radius.rb:3msgid "tag|example|Here's an example"msgstr ""{code}Finally, we don't want to translate code examples, obviously{code} # @example Using the type.#: ../lib/puppet/type/test.rb:3msgid "test { 'mctesterson':\n"" foo => 'hi',\n"" my_prop => 'bar',\n""}"msgstr ""{code}
Add Comment
This message was sent by
Jira (PDOC-207) i18n in puppet-strings
Title: Message Title
Eric Putnam updated an issue
Puppet Strings / PDOC-207
i18n in puppet-strings
Change By:
Eric Putnam
See PDOC-193 for info on existing yard tool. You can see this in raw action by simply calling the CLI tool from the PuppetStrings.generate method and then running strings on a module.{code:ruby}YARD::CLI::I18n.run(search_patterns){code}You can see from the attached file, there's a lot of stuff that we won't want in there. It will be confusing to the translator and lots of unnecessary work. A few examples:A lot of tags get the tag itself extracted into a msgid that looks like the one here:{code}# @param [String]#: ../lib/puppet/type/radius.rb:3#: ../manifests/install.pp:10msgid "tag|param|name"msgstr ""{code}First of all, we don't want the param name translated. Second, that's just confusing to look at.In other cases, we _do_ want part of this msgid. This mostly occurs in examples:{code}# @example#: ../lib/puppet/type/radius.rb:3msgid "tag|example|Here's an example"msgstr ""{code}Finally, we don't want to translate code examples, obviously{code} # @example Using the type.#: ../lib/puppet/type/test.rb:3msgid "test { 'mctesterson':\n"" foo => 'hi',\n"" my_prop => 'bar',\n""}"msgstr ""{code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-559) Create rake task to generate reference documentation
Title: Message Title Michael Smith commented on BOLT-559 Re: Create rake task to generate reference documentation Is our plan to check docs for Bolt and its modules into the repo? 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-6185) Windows stat / lstat are inefficient - may calculate mode too frequently
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6185 Windows stat / lstat are inefficient - may calculate mode too frequently Change By: Josh Cooper Team: Platform Core Windows 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 (PDOC-193) Evaluate using `yard i18n` to extract doc string content into POT files
Title: Message Title Eric Putnam updated an issue Puppet Strings / PDOC-193 Evaluate using `yard i18n` to extract doc string content into POT files Change By: Eric Putnam Attachment: yard.pot 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 (PDOC-193) Evaluate using `yard i18n` to extract doc string content into POT files
Title: Message Title
Eric Putnam updated an issue
Puppet Strings / PDOC-193
Evaluate using `yard i18n` to extract doc string content into POT files
Change By:
Eric Putnam
Since 0.8.0 yard has included an {{i18n}} subcommand to place all the doc strings into a .pot file. It seems like if we just run this automatically when a user invokes {{puppet strings}} that would go a long way to enabling i18n workflows for module documentation. You can see this in raw action by simply calling the CLI tool from the PuppetStrings.generate method and then running strings on a module.{code}YARD::CLI::I18n.run(search_patterns){code}
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 (PDOC-193) Evaluate using `yard i18n` to extract doc string content into POT files
Title: Message Title
Eric Putnam updated an issue
Puppet Strings / PDOC-193
Evaluate using `yard i18n` to extract doc string content into POT files
Change By:
Eric Putnam
Since 0.8.0 yard has included an {{i18n}} subcommand to place all the doc strings into a .pot file. It seems like if we just run this automatically when a user invokes {{puppet strings}} that would go a long way to enabling i18n workflows for module documentation.You can see this in raw action by simply calling the CLI tool from the PuppetStrings.generate method and then running strings on a module.{code :ruby }YARD::CLI::I18n.run(search_patterns){code}
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 (FACT-1862) add support for openSUSE LEAP 15
Title: Message Title Branan Riley commented on FACT-1862 Re: add support for openSUSE LEAP 15 We don't really support openSUSE. We're happy to take patches, but can't promise we'll do this ourselves. We will be doing work to enable SLES 15 very soon, but I can't promise that will make openSUSE 15 work correctly (It probably will work, but I don't like making promises I can't keep) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1862) add support for openSUSE LEAP 15
Title: Message Title
Branan Riley updated an issue
Facter / FACT-1862
add support for openSUSE LEAP 15
Change By:
Branan Riley
Please add support for the current openSUSE release (LEAP 15.0) in facter - the upcoming SUSE enterprise version 15 (SLES 15) will share the same code base, so this should be done anyway. Current output of facter (version 3.11.1) on LEAP 15.0:{noformat}os => { architecture => "x86_64", family => "Linux", hardware => "x86_64", name => "Linux", release => {full => "4.12.14-lp150.12.4-default",major => "4",minor => "12" }, selinux => {enabled => false }}{noformat}Output on previous version (LEAP 42.3):{noformat}os => { architecture => "x86_64", family => "Suse", hardware => "x86_64", name => "OpenSuSE", release => {full => "42.3",major => "42",minor => "3" }, selinux => {enabled => false }}{noformat}
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
Jira (FACT-1862) add support for openSUSE LEAP 15
Title: Message Title
Branan Riley updated an issue
Facter / FACT-1862
add support for openSUSE LEAP 15
Change By:
Branan Riley
Environment:
Current output of facter (version 3.11.1) on LEAP 15.0:{noformat}os => { architecture => "x86_64", family => "Linux", hardware => "x86_64", name => "Linux", release => {full => "4.12.14-lp150.12.4-default",major => "4",minor => "12" }, selinux => {enabled => false }}{noformat}Output on previous version (LEAP 42.3):{noformat}os => { architecture => "x86_64", family => "Suse", hardware => "x86_64", name => "OpenSuSE", release => {full => "42.3",major => "42",minor => "3" }, selinux => {enabled => false }}{noformat}
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-8919) Add selinux user to Puppet User Resource
Title: Message Title Branan Riley updated an issue Puppet / PUP-8919 Add selinux user to Puppet User Resource Change By: Branan Riley Labels: linux selinux type_and_provider 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-579) I want to know what output format bolt is using
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-579 I want to know what output format bolt is using Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-579) I want to know what output format bolt is using
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-579 I want to know what output format bolt is using Issue Type: New Feature Assignee: Unassigned Created: 2018/06/08 1:48 PM Priority: Normal Reporter: Alex Dreyer How many people use the Human vs JSON output formats. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-3935) Determine retirements, if any, for pdb 6
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3935 Determine retirements, if any, for pdb 6 Issue Type: Improvement Affects Versions: PDB 6.0.0 Assignee: Unassigned Created: 2018/06/08 12:33 PM 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
Jira (PDB-3934) Determine deprecations, if any for pdb 6
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3934 Determine deprecations, if any for pdb 6 Issue Type: Improvement Affects Versions: PDB 6.0.0 Assignee: Unassigned Created: 2018/06/08 12:32 PM 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
Jira (PDB-3560) Uncomment file-with-binary-template test once the relevant puppet pr is merged
Title: Message Title Rob Browning commented on PDB-3560 Re: Uncomment file-with-binary-template test once the relevant puppet pr is merged Now that this is merged into 5.1.x, I'm leaving the ticket open until we finish merging it up to master (and make sure it's fine with the other branches' agent integration test versions). 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-8919) Add selinux user to Puppet User Resource
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8919 Add selinux user to Puppet User Resource Change By: Josh Cooper Team: Platform 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-578) I want to know how popular bundled module content is
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-578 I want to know how popular bundled module content is Issue Type: New Feature Assignee: Unassigned Created: 2018/06/08 11:41 AM Priority: Normal Reporter: Alex Dreyer I want to track how often the tasks and plans that are bundled with bolt are used. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8484) Update ruby 1.9.3 code paths
Title: Message Title Ethan Brown commented on PUP-8484 Re: Update ruby 1.9.3 code paths Merged to master in https://github.com/puppetlabs/puppet/commit/4e07f3768182bd201786adc8eea0f567cf28301a 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-3502) Puppet provider fails on first run if features are delivered during run (Windows)
Title: Message Title Josh Cooper commented on PUP-3502 Re: Puppet provider fails on first run if features are delivered during run (Windows) I recently discovered that the agent does not use the correct environment when loading features to determine provider suitability: https://github.com/puppetlabs/puppet/pull/6867/files#diff-f6dce0fbcf55caef42fe28d46c33e340R51. I'm wondering if this is related to the issue you're seeing? I'm not sure why the behavior would be different on Windows vs Unix though. 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-6729) NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators
Title: Message Title Ethan Brown commented on PUP-6729 Re: NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators Yeah, the symptoms are the same, but I think the cause is different. Let's spin off a new ticket for this new repro, which has deviated quite a bit from the original description. 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-3262) By default, the cadir should be separated from the ssldir
Title: Message Title Maggie Dreyer commented on PUP-3262 Re: By default, the cadir should be separated from the ssldir Eric Sorenson When we say that existing installations should look in the old CA dir first, do we mean to only look in the default location, or to respect the old setting? This has implications for when/how we remove the CA's Ruby dependency. 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-8919) Add selinux user to Puppet User Resource
Title: Message Title
Sean A created an issue
Puppet / PUP-8919
Add selinux user to Puppet User Resource
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2018/06/08 8:36 AM
Priority:
Normal
Reporter:
Sean A
Puppet Version: Any Puppet Server Version: Any OS Name/Version: RHEL OS Family, or any SELinux enabled system Would like to be able to set the selinux 'user' context for a linux user via puppet user resource. This equates to the user resource having access to useradd's -Z flag. We are required to set all linux systems to have a default selinux user context that is not unconfined_u, and assign all system users to an selinux user that applies user_u or staff_u context to the user. Today my puppet code which manages accounts (not puppetlabs-accounts module) must use exec resources to assign a user to the appropriate selinux user. It would be nice to just have an param in Puppet's user resource to make this happen. Desired Behavior: user { 'test-admin': ensure => present, selinux => $::selinux_admins, ... }user { 'test-user': ensure => present, selinux => $::selinux_users, ... } Actual Behavior: User resource is not yet capable of allowing customization for selinux user contexts. There also do not seem to be puppet resources relating to selinux logins or user contexts, but that is more manageable outside of a puppet resource, because it's a define once per system kind of thing, whereas this selinux user role is defined per user, and using exec resources get messy to undo when setting the user to absent.
Jira (PUP-8918) Separate CA and SSL dirs
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-8918 Separate CA and SSL dirs Issue Type: Epic Assignee: Unassigned Created: 2018/06/08 8:29 AM Priority: Normal Reporter: Maggie Dreyer This epic contains the work for separating puppetserver's CA dir from Puppet's SSL dir. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-3560) Uncomment file-with-binary-template test once the relevant puppet pr is merged
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3560 Uncomment file-with-binary-template test once the relevant puppet pr is merged Change By: Rob Browning Assignee: 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 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-8908) Resource status of "failed_to_restart" is not included in reports for individual resources
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8908 Resource status of "failed_to_restart" is not included in reports for individual resources Change By: Jacob Helwig Fix Version/s: PUP 6.0.0 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-8908) Resource status of "failed_to_restart" is not included in reports for individual resources
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-8908 Resource status of "failed_to_restart" is not included in reports for individual resources Change By: Jacob Helwig Fix Version/s: PUP 5.3.z Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1862) add support for openSUSE LEAP 15
Title: Message Title
Michael Geiger created an issue
Facter / FACT-1862
add support for openSUSE LEAP 15
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2018/06/08 3:12 AM
Environment:
Current output of facter (version 3.11.1) on LEAP 15.0:
os => {
architecture => "x86_64",
family => "Linux",
hardware => "x86_64",
name => "Linux",
release => {
full => "4.12.14-lp150.12.4-default",
major => "4",
minor => "12"
},
Jira (PUP-3180) Puppet should deprecate the use of CRLs and move towards OCSP
Title: Message Title Sina Anvari commented on PUP-3180 Re: Puppet should deprecate the use of CRLs and move towards OCSP Are there any new updates on this? 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.
