Jira (PUP-3320) Could not find declared class
Title: Message Title Vishwanath Hegde commented on PUP-3320 Re: Could not find declared class Thanks for the update.Will check in Slack or IRC. On 09-Jan-2018 6:31 PM, "Henrik Lindberg (JIRA)" < 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-1793) Facter incorrectly outputs backslash characters in default output
Title: Message Title Glenn Sarti commented on FACT-1793 Re: Facter incorrectly outputs backslash characters in default output Ha yeah...It threw me as well. 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-8337) Package source on Windows errors out on deduped installation files
Title: Message Title Ethan Brown commented on PUP-8337 Re: Package source on Windows errors out on deduped installation files IO_REPARSE_TAG_DEDUP - that's a new one to me! Your assessment is basically correct Branan Riley. We check a path to see if it's a symlink by looking at the Attributes struct returned https://msdn.microsoft.com/en-us/library/windows/desktop/aa365739(v=vs.85).aspx. If FILE_ATTRIBUTE_REPARSE_POINT is set at https://github.com/puppetlabs/puppet/blob/80020936a25cbb8b1850518d21d02d38420fdac5/lib/puppet/util/windows/file.rb#L236 then we consider it a symlink. If set, then we use DeviceIoControl API to fill a struct with more details, but we only understand what to do with the more common REPARSE_TAG_MOUNT_POINT and REPARSE_TAG_SYMLINK per https://github.com/puppetlabs/puppet/blob/80020936a25cbb8b1850518d21d02d38420fdac5/lib/puppet/util/windows/file.rb#L187-L190 I think the best solution may be to modify the symlink? check to only return true for symlinks and mount points given we can't currently do anything with the others anyhow... 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 Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-266 Log run_* actions when called from a plan Change By: Michael Smith Assignee: Alex Dreyer 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-8066) Failing acceptance tests in FIPS mode
Title: Message Title Josh Cooper commented on PUP-8066 Re: Failing acceptance tests in FIPS mode Passed CI in 2317a85efc8ffdcba36f0e478ca944e1eb0b9459, no additional validation needed. 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-8066) Failing acceptance tests in FIPS mode
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8066 Failing acceptance tests in FIPS mode Change By: Josh Cooper Release Notes: Not Needed 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-8082) Add warning to Puppet Module Tool when installing a deprecated module
Title: Message Title Jesse Scott commented on PUP-8082 Re: Add warning to Puppet Module Tool when installing a deprecated module Josh Cooper Thanks, I'll work on release notes and verification tomorrow. 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-8082) Add warning to Puppet Module Tool when installing a deprecated module
Title: Message Title Josh Cooper commented on PUP-8082 Re: Add warning to Puppet Module Tool when installing a deprecated module Jesse Scott, Eric Putnam could add release notes and verify the fix is working as intended in the most recent puppet-agent#master build. SHA de540d2ba023183f6c7a65b3d16ca867e98516df should contain your changes. 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-8082) Add warning to Puppet Module Tool when installing a deprecated module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8082 Add warning to Puppet Module Tool when installing a deprecated module Change By: Josh Cooper Component/s: PMT 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-8082) Add warning to Puppet Module Tool when installing a deprecated module
Title: Message Title Josh Cooper commented on PUP-8082 Re: Add warning to Puppet Module Tool when installing a deprecated module Merged to master in https://github.com/puppetlabs/puppet/commit/b2e212e7282657069505546419c7773b9274c5b5. 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-8285) filebucket backup with an alternate bucket may not backup
Title: Message Title Josh Cooper commented on PUP-8285 Re: filebucket backup with an alternate bucket may not backup Merged to master in https://github.com/puppetlabs/puppet/commit/69b02d473e5811de1eadc5eab068692c88828276. 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-8285) filebucket backup with an alternate bucket may not backup
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8285 filebucket backup with an alternate bucket may not backup Change By: Josh Cooper Assignee: Josh Cooper 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 Josh Cooper updated an issue Puppet / PUP-8122 I18n strings that include repeated lists of sentence fragments can be hard to translate Change By: Josh Cooper Release Notes: Not Needed 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-4065) errors/warnings in environment.conf should not be duplicated
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4065 errors/warnings in environment.conf should not be duplicated Change By: Josh Cooper Release Notes Summary: If environment.conf contains unknown settings, puppet will now only warn once for each unknown setting. 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-8338) Puppet apply doesn't stream file content
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8338
Puppet apply doesn't stream file content
Change By:
Josh Cooper
*Puppet Version:* Puppet 4 (at least) and up*Puppet Server Version:* n/a*OS Name/Version:* allWhen running {{puppet apply}} with a file resource whose and source parameter is {{http(s)}} or {{puppet}} , then puppet will load the entire file into memory, instead of streaming it. Note the {{puppet}} case only happens if a host isn't specified, as that is interpreted to mean "use the local fileserver". This was noticed while researching why the bug described in PUP-7482 only affected {{puppet agent}} but not {{puppet apply}}.*Desired Behavior:*When managing files with a {{source}} parameter, puppet apply should always stream file content from all of the following sources{{}} local file{{file://}} local file{{puppet:///modules/mymodule}} local file{{http?://host:port/path/to/file}} remote file*Actual Behavior:*{{puppet apply}} does not stream file content from http-based sources. See https://github.com/puppetlabs/puppet/blob/5.3.3/lib/puppet/type/file/source.rb#L274-L276.At first glance it appears the {{Puppet::Type::File::ParameterSource#content}} method can be deleted entirely, and should always rely on {{ chunk_file_from_source chunk_file_from_disk }} which will invoke the or {{ terminus_selector.rb chunk_file_from_source }} to determine the correct source .
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
Jira (BOLT-268) Investigate using log4r for logging and stdoutoutput in bolt
Title: Message Title Nick Lewis commented on BOLT-268 Re: Investigate using log4r for logging and stdoutoutput in bolt Bonus: we already have a transitive dependency on logging via the winrm gem. 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-8338) Puppet apply doesn't stream file content
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8338 Puppet apply doesn't stream file content Change By: Josh Cooper Summary: Puppet apply doesn't stream remote file content 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-8338) Puppet apply doesn't stream remote file content
Title: Message Title Josh Cooper created an issue Puppet / PUP-8338 Puppet apply doesn't stream remote file content Issue Type: Bug Assignee: Unassigned Created: 2018/01/09 4:11 PM Priority: Normal Reporter: Josh Cooper Puppet Version: Puppet 4 (at least) and up Puppet Server Version: n/a OS Name/Version: all When running puppet apply with a file resource whose source parameter is http(s) or puppet, then puppet will load the entire file into memory, instead of streaming it. Note the puppet case only happens if a host isn't specified, as that is interpreted to mean "use the local fileserver". This was noticed while researching why the bug described in PUP-7482 only affected puppet agent but not puppet apply. Desired Behavior: When managing files with a source parameter, puppet apply should always stream file content from all of the following sources local file file:// local file puppet:///modules/mymodule local file http?://host:port/path/to/file remote file Actual Behavior: puppet apply does not stream file content from http-based sources. See https://github.com/puppetlabs/puppet/blob/5.3.3/lib/puppet/type/file/source.rb#L274-L276. At first glance it appears the Puppet::Type::File::ParameterSource#content method can be deleted entirely, and should always rely on chunk_file_from_source which will invoke the terminus_selector.rb to determine the correct source.
Jira (PUP-5993) Possible intermittent test failure in registry_spec.rb
Title: Message Title Glenn Sarti commented on PUP-5993 Re: Possible intermittent test failure in registry_spec.rb registry no longer runs spec tests on Jenkins. This is now a non-issue 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-268) Investigate using log4r for logging and stdoutoutput in bolt
Title: Message Title Alex Dreyer commented on BOLT-268 Re: Investigate using log4r for logging and stdoutoutput in bolt sounds promising 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-8337) Package source on Windows errors out on deduped installation files
Title: Message Title Branan Riley commented on PUP-8337 Re: Package source on Windows errors out on deduped installation files My reading of the code associated with this error is that we have an assumption that we can treat reparse points as approximately "symlinks", and it fails on reparse point tags that don't make sense for that. We might need to be a little bit smarter about which reparse point types require various sorts of special handling. But I'm not an expert in any of the windows FS code in Puppet, so grain of salt here. 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-8337) Package source on Windows errors out on deduped installation files
Title: Message Title Glenn Sarti commented on PUP-8337 Re: Package source on Windows errors out on deduped installation files Software based dedupe https://docs.microsoft.com/en-us/windows-server/storage/data-deduplication/understand https://msdn.microsoft.com/en-us/library/windows/desktop/aa365511(v=vs.85).aspx #define IO_REPARSE_TAG_MOUNT_POINT (0xA003L) #define IO_REPARSE_TAG_HSM (0xC004L) #define IO_REPARSE_TAG_HSM2 (0x8006L) #define IO_REPARSE_TAG_SIS (0x8007L) #define IO_REPARSE_TAG_WIM (0x8008L) #define IO_REPARSE_TAG_CSV (0x8009L) #define IO_REPARSE_TAG_DFS (0x800AL) #define IO_REPARSE_TAG_SYMLINK (0xA00CL) #define IO_REPARSE_TAG_DFSR (0x8012L)
Jira (BOLT-268) Investigate using log4r for logging and stdoutoutput in bolt
Title: Message Title Nick Lewis commented on BOLT-268 Re: Investigate using log4r for logging and stdoutoutput in bolt The log4r library looks unmaintained. We just passed the 4 year anniversary of its most recent commit, and the 6 year anniversary of its most recent release to rubygems. However, the logging library looks quite promising. It's almost modeled after log4j, and supports many features that would be beneficial: • defining multiple appenders • different log levels for different loggers • lookup of loggers and appenders by name • additivity (passing logs up to the parent), which I think should mean we can squelch net::ssh messages by passing it a particularly configured logger • various formats (per appender): plain, inspect, json, yaml • log rotation • custom log levels • color schemes, and it will handle coloring them itself • deferred log evaluation with block evaluation • Mapped Diagnostic Context, which seems to mean basically thread-local context that's interpolated into the log pattern (node name, for instance?) • rspec integration to capture log messages It looks like the default logger is functionally identical to the built-in ruby logger, so we could swap this in trivially and build out from there. 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-268) Investigate using log4r for logging and stdoutoutput in bolt
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-268 Investigate using log4r for logging and stdoutoutput in bolt Change By: Nick Lewis Assignee: Nick Lewis 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-8337) Package source on Windows errors out on deduped installation files
Title: Message Title Branan Riley updated an issue Puppet / PUP-8337 Package source on Windows errors out on deduped installation files Change By: Branan Riley Team: Windows 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-8337) Package source on Windows errors out on deduped installation files
Title: Message Title Branan Riley moved an issue Puppet / PUP-8337 Package source on Windows errors out on deduped installation files Change By: Branan Riley Affects Version/s: puppet-agent 5.3.3 Affects Version/s: PUP 5.3.3 Component/s: Windows Component/s: Windows Key: PA PUP - 1717 8337 Project: Puppet Agent Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-7482) Agent sends wrong content-type when using http file sources
Title: Message Title Kris Bosland commented on PUP-7482 Re: Agent sends wrong content-type when using http file sources Merged into 4.10.x at https://github.com/puppetlabs/puppet/commit/e9d8a4bb9248c3916c9b249c6ec364edb6bf1ba3. 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-7482) Agent sends wrong content-type when using http file sources
Title: Message Title Kris Bosland updated an issue Puppet / PUP-7482 Agent sends wrong content-type when using http file sources Change By: Kris Bosland Comment: Merged into 4.10.x at https://github.com/puppetlabs/puppet/commit/e9d8a4bb9248c3916c9b249c6ec364edb6bf1ba3. 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-1743) Environment variable override for structured facts
Title: Message Title Branan Riley commented on FACT-1743 Re: Environment variable override for structured facts As a workaround, you can lay down a .json or .yaml file in Facter's external facts directory, containing the entire structure you wish to override. EX: --- os: family: ... ... We don't currently provide a way to override just a subset of any structured fact, although it's definitely a feature that's been requested before. Also: Have you filed a ticket for the misdetected OS version? I'd like us to be able to resolve that for you as well, if possible. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-7482) Agent sends wrong content-type when using http file sources
Title: Message Title Melissa Stone commented on PUP-7482 Re: Agent sends wrong content-type when using http file sources Merged into 4.10.x at https://github.com/puppetlabs/puppet/commit/e9d8a4bb9248c3916c9b249c6ec364edb6bf1ba3 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-1776) FreeBSD network facts resolution surprise
Title: Message Title Branan Riley updated an issue Facter / FACT-1776 FreeBSD network facts resolution surprise Change By: Branan Riley Team: Platform OS 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-1776) FreeBSD network facts resolution surprise
Title: Message Title Branan Riley commented on FACT-1776 Re: FreeBSD network facts resolution surprise Those are not link-local or loopback addresses, so I agree - Facter should consider them as potential resolutions for ipaddress6. 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-1793) Facter incorrectly outputs backslash characters in default output
Title: Message Title Branan Riley updated an issue Facter / FACT-1793 Facter incorrectly outputs backslash characters in default output Change By: Branan Riley Team: Platform OS 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-1793) Facter incorrectly outputs backslash characters in default output
Title: Message Title Branan Riley commented on FACT-1793 Re: Facter incorrectly outputs backslash characters in default output Yeah. The "rubyish" output is probably worth us manually adding escaping to. I totally thought that was the JSON output when I went through this the first time, sorry! 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-1806) Windows KVM host not recognized as virtual
Title: Message Title Branan Riley commented on FACT-1806 Re: Windows KVM host not recognized as virtual Since you're on a modern Facter release, would you mind also trying the output of facter hypervisors? That will let us know if the library we're working on to clean up the virtual fact is working in your use case or not, and might help track this down more quickly. 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-1794) os.family.major incorrectly returns a number with a decimal point for Ubuntu
Title: Message Title Branan Riley commented on FACT-1794 Re: os.family.major incorrectly returns a number with a decimal point for Ubuntu In this case, I would expect os.realease.full to be "16.04.3", which would make having the two fields useful, and would make our interpretation of what's the "major" part make more sense. We likely won't fix this until Facter 4, since messing with fact values in stable releases is always frustrating to users. There was definitely an intentional decision to treat the date portion of an Ubuntu release as a single field for the sake of splitting up the version. If you think of a set of Red Hat releases like '7.1', '7.2', '7.3' all grouped as 'Red Hat 7', the same pattern for Ubuntus is '16.04.1', '16.04.2', '16.04.3' being grouped as 'Ubuntu 16.04' We want the major field to have the same semantics in both cases. Ubuntu's usage of a period in the date field is unfortunate, because it makes it look like it should be an X.Y.Z version. It is not. The correct way to parse it is [date].[patch]. Trying to report just the year from an Ubuntu release is of similar fragility to saying "Fedora 25 and 26 are similar enough that I can manage both with the same code - I want Facter to report version '2' to me". You're welcome to use a custom fact if you really, really need that capability, but it's not a pattern I would want to encourage most users to follow. 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-1503) catalog contains duplicate classes
Title: Message Title Maggie Dreyer commented on PUP-1503 Re: catalog contains duplicate classes This is reproducible in the classroom setup for the Puppet Practitioner course, where classification was done via the PE console. The userprefs class, which I think comes from this module https://forge.puppet.com/pltraining/userprefs, appears in the file twice, consistently enough that there is a reminder in the lecture notes that makes reference to this ticket. Another student in the class who did classification manually via site.pp did not see the duplicate entry. 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-8300) File resource can't handle HTTP redirects when server does not accept HEAD requests
Title: Message Title Josh Cooper commented on PUP-8300 Re: File resource can't handle HTTP redirects when server does not accept HEAD requests Thanks [~Mariusz Gronczewski] I think this is a duplicate of PUP-6380. Can you review, and close this ticket if that's the case? One note, puppet makes a HEAD request to get metadata about the file, so that it doesn't download the file if it doesn't need to. If it wasn't for that, then puppet could skip HEAD requests altogether. 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 (HI-558) Automate smoke-test of hiera gem release artifacts
Title: Message Title Geoff Nichols updated an issue Hiera / HI-558 Automate smoke-test of hiera gem release artifacts Change By: Geoff Nichols Sprint: Platform OS Kanban Ready for Eng. 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-7290) Automate smoke-test of puppet gem release artifacts
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7290 Automate smoke-test of puppet gem release artifacts Change By: Geoff Nichols Sprint: Platform OS Kanban Ready for Eng. 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 Kris Bosland updated an issue Puppet / PUP-7630 "Successful" puppet agent reports hide provider errors Change By: Kris Bosland 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 (BOLT-285) Bolt should handle parser errors better
Title: Message Title
Michael Smith commented on BOLT-285
Re: Bolt should handle parser errors better
Some examples of current error behavior
raise Puppet::ParseErrorWithIssue.from_issue_and_stack(Puppet::Pops::Issues::TASK_OPERATION_NOT_SUPPORTED_WHEN_COMPILING, operation: 'run_command')
#Error: The task operation 'run_command' is not available when compiling a catalog at /foo.pp:6 on node bar
raise Puppet::ParseError, 'Task parameters is not of type Data'
#Error: Evaluation Error: Error while evaluating a Function Call, Task parameters is not of type Data at /foo.pp:6:11 on node bar
raise ArgumentError, "Function #{self.class.name}(): Unknown plan: '#{task_name}'"
#Error: Evaluation Error: Error while evaluating a Function Call, Function run_task(): Unknown task: 'foo' at /foo.pp:6:11 on node bar
Jira (PUP-7630) "Successful" puppet agent reports hide provider errors
Title: Message Title Kris Bosland commented on PUP-7630 Re: "Successful" puppet agent reports hide provider errors Fix merged into 4.10.x at https://github.com/puppetlabs/puppet/commit/e58f47581365541db09318aff697d93397ece31c. 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 Kris Bosland updated an issue Puppet / PUP-7630 "Successful" puppet agent reports hide provider errors Change By: Kris Bosland Fix Version/s: PUP 6.0.0 Fix Version/s: PUP 4.10.z 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-8212) The Variant type without any types matches in strange ways
Title: Message Title Michael Smith updated an issue Puppet / PUP-8212 The Variant type without any types matches in strange ways Change By: Michael Smith 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-8285) filebucket backup with an alternate bucket may not backup
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8285 filebucket backup with an alternate bucket may not backup Change By: Josh Cooper Release Notes Summary: Updates documentation that the `--bucket` option implies `--local` and overrides the default directory`$clientbucketdir`.When using the `--bucket` option, a file to be backed up was not actually backed up, if the file already existed in the default bucket $clientbucketdir location. 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 (PDOC-196) Documentation misleading about acceptable tags
Title: Message Title Lee Lowder created an issue Puppet Strings / PDOC-196 Documentation misleading about acceptable tags Issue Type: Bug Affects Versions: PDOC 1.1.1 Assignee: Unassigned Created: 2018/01/09 11:31 AM Environment: Strings 1.1.1, yard 0.9.9, Ruby 2.1.9p490 (2016-03-30 revision 54437) [i386-mingw32], puppet 4.5.3 on win7 Strings command ran from a "Start command prompt with puppet" instance, non-admin user Priority: Normal Reporter: Lee Lowder The docs for Strings states: The most commonly used tags for Strings are: ... For a complete list of tags, see the YARD Tags Overview. This implies that while the tags in the list are the most often used ones, any valid tag can be used. However, when I used the @todo and @note tags they did not show up in my rendered HTML documentation as expected. This ticket is intended to request that support for the additional tags be added, and that the documentation be updated to reflect actual behavior in the mean time since adding the tags may be non-trivial.
Jira (BOLT-282) Update hands on lab Vagrantfile
Title: Message Title Michael Smith assigned an issue to Nick Lewis Puppet Task Runner / BOLT-282 Update hands on lab Vagrantfile Change By: Michael Smith Assignee: Nick Lewis 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-8314) i18n add string decorations to "raise ArgumentError" call
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8314 i18n add string decorations to "raise ArgumentError" call Change By: Eric Delaney Sprint: Platform Core Grooming 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-8136) refactor Puppet::Parameter.format so that we can avoid using %s in strings
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8136 refactor Puppet::Parameter.format so that we can avoid using %s in strings Change By: Eric Delaney Sprint: Platform Core Hopper 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-8136) refactor Puppet::Parameter.format so that we can avoid using %s in strings
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8136 refactor Puppet::Parameter.format so that we can avoid using %s in strings 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-8322) 18n add string decorations to "raise EventLogError" call
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8322 18n add string decorations to "raise EventLogError" call 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-8324) i18n add string decorations to "raise Puppet::Error" call
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8324 i18n add string decorations to "raise Puppet::Error" call 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-8321) Update how warn_once prints the file and line location of messages
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8321 Update how warn_once prints the file and line location of messages 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-8025) `puppet module install` does not correctly install locale files
Title: Message Title Eric Putnam commented on PUP-8025 Re: `puppet module install` does not correctly install locale files Continued testing using these steps: 1. Install module from local tarball 2. Create additional files in locales/ (modulename.pot, then ja/modulename.po) 3. Build module with new files 4. Uninstall module 5. Install module from new tarball All files are still in the installed version as expected. Maggie Dreyer do you have a minute to try installing a few times again just to see if you still see it happening (i.e. is it possibly environmental?)? 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-8218) Error 500 on SERVER: Server Error: A duplicate resource was found while collecting exported resources
Title: Message Title Alex P commented on PUP-8218 Re: Error 500 on SERVER: Server Error: A duplicate resource was found while collecting exported resources to add the my comment above, if you do that additional line on Host B, then the Puppet Server log message will say: Server Error: A duplicate resource was found while collecting exported resources, with the type and title Host[host-a.domain.com] on node host-a.domain.com So, it'll be pointing to and blaming Host A, but not the other one. 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-8218) Error 500 on SERVER: Server Error: A duplicate resource was found while collecting exported resources
Title: Message Title Thomas Hallgren commented on PUP-8218 Re: Error 500 on SERVER: Server Error: A duplicate resource was found while collecting exported resources Sounds like this could be related to PDB-3734. 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-8312) i18n add string decorations to Puppet.err() and Puppet.warning() calls and raise InterpolationError strings
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8312 i18n add string decorations to Puppet.err() and Puppet.warning() calls and raise InterpolationError strings Change By: Eric Delaney In the Puppet code when we call Puppet.err() and Puppet.warning() the string calls and raise InterpolationError strings passed most likely should be internationalized. 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-8312) i18n add string decorations to Puppet.err() and Puppet.warning() calls and raise InterpolationError strings
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8312 i18n add string decorations to Puppet.err() and Puppet.warning() calls and raise InterpolationError strings Change By: Eric Delaney Summary: i18n add string decorations to Puppet.err() and Puppet.warning() calls and raise InterpolationError strings 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-8312) i18n add string decorations to Puppet.err() and Puppet.warning() calls and raise InterpolationError strings
Title: Message Title Eric Delaney updated an issue Puppet / PUP-8312 i18n add string decorations to Puppet.err() and Puppet.warning() calls and raise InterpolationError strings Change By: Eric Delaney Acceptance Criteria: - Review calls to Puppet.err() and Puppet.warning() and raise InterpolationError strings and determine which need string decorations for i18n- unit tests updated and passing- acceptance tests updated and passing 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-289) Standardize Target object
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-289 Standardize Target object Change By: David Kramer Sprint: Bolt Ready for Grooming 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 (BOLT-289) Standardize Target object
Title: Message Title
David Kramer updated an issue
Puppet Task Runner / BOLT-289
Standardize Target object
Change By:
David Kramer
The Target datatype from puppet was moved into bolt. We should move the NodeURI logic into Target and update the Executor and Node classes to interact with targets objects. Changes:- The Target class should be updated to expose the expected accessors.- The Target class should have a {{from_uri}} class method to create a Target from a url. unspecified options should be nil- The Target class should have a {{parse_urls}} class method to create an array of Target objects from a --nodes argument.- The Node initializer should take a single target object and save it instead of saving various options from config and the url separately. - Unspecified options(port, user password etc) should be nil- Bolt::Node.from_uri should become Bolt::Node.from_target- The executor should accept a list of target objects.- The CLI and run_* functions should pass an array of Target objects to the executor- Bolt::Result should include the Target * Target class * * Class methods: * from_uriparse_urls * Instance accessors: * protocoluserpasswordhostnameporttransport_options(options on the target that come from the config and transport specific flags)urlto_s -> url
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
Jira (BOLT-289) Standardize Target object
Title: Message Title
David Kramer updated an issue
Puppet Task Runner / BOLT-289
Standardize Target object
Change By:
David Kramer
The Target datatype from puppet was moved into bolt. We should move the NodeURI logic into Target and update the Executor and Node classes to interact with targets objects. Changes:- The Target class should be updated to expose the expected accessors.- The Target class should have a {{from_uri}} class method to create a Target from a url. unspecified options should be nil- The Target class should have a {{parse_urls}} class method to create an array of Target objects from a --nodes argument.- The Node initializer should take a single target object and save it instead of saving various options from config and the url separately. - Unspecified options(port, user password etc) should be nil- Bolt::Node.from_uri should become Bolt::Node.from_target- The executor should accept a list of target objects.- The CLI and run_* functions should pass an array of Target objects to the executor Possible Changes: - Bolt::Result should include the Target(perhaps hidden from pcore)Target classClass methods:from_uriparse_urlsInstance accessors:protocoluserpasswordhostnameporttransport_options(options on the target that come from the config and transport specific flags)urlto_s -> url
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
Jira (BOLT-289) Standardize Target object
Title: Message Title
David Kramer updated an issue
Puppet Task Runner / BOLT-289
Standardize Target object
Change By:
David Kramer
The Target datatype from puppet was moved into bolt. We should move the NodeURI logic into Target and update the Executor and Node classes to interact with targets objects. Changes:- The Target class should be updated to expose the expected accessors.- The Target class should have a {{from_uri}} class method to create a Target from a url. unspecified options should be nil- The Target class should have a {{parse_urls}} class method to create an array of Target objects from a --nodes argument.- The Node initializer should take a single target object and save it instead of saving various options from config and the url separately. - Unspecified options(port, user password etc) should be nil- Bolt::Node.from_uri should become Bolt::Node.from_target- The executor should accept a list of target objects.- The CLI and run_* functions should pass an array of Target objects to the executor- Bolt::Result should include the Target (perhaps hidden from pcore) Target classClass methods:from_uriparse_urlsInstance accessors:protocoluserpasswordhostnameporttransport_options(options on the target that come from the config and transport specific flags)urlto_s -> url
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
Jira (BOLT-301) Transports
Title: Message Title Yasmin Rajabi created an issue Puppet Task Runner / BOLT-301 Transports Issue Type: Epic Assignee: Unassigned Created: 2018/01/09 9:55 AM Priority: Normal Reporter: Yasmin Rajabi 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-277) SSL default makes winrm harder to use
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-277 SSL default makes winrm harder to use Change By: David Kramer Sprint: Bolt Ready for Grooming 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 (BOLT-290) Decompose --insecure flag
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-290
Decompose --insecure flag
Change By:
Michael Smith
The --insecure flag has a different meaning for different transports and is not specific enough for future features.SSH:For ssh we should replace the {{\ - \ -insecure }} flag with {{\ - \ - \[ no \ - \] host-key-check }} . In the config we should expose a {{ host-key-check }} option that defaults to true.WINRM:for the winrm transport we should replace {{\ - \ -insecure }} with {{\ - \ - ssl and -- \[ no \ - \] ssl }} on the commandline. In the config we should have a single {{ ssl }} option that defaults to to true.
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-290) Decompose --insecure flag
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-290 Decompose --insecure flag Change By: David Kramer The --insecure flag has a different meaning for different transports and is not specific enough for future features.SSH:For ssh we should replace the --insecure flag with --no-host-key-check. In the config we should expose a host-key-check option that defaults to true.WINRM:for the winrm transport we should replace --insecure with --ssl / and --no-ssl on the commandline. In the config we should have a single ssl option that defaults to to true. 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-290) Decompose --insecure flag
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-290 Decompose --insecure flag Change By: David Kramer Sprint: Bolt Ready for Grooming 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-3321) config set adds a preceding newline to value if previous value was empty
Title: Message Title Jorie Tappa assigned an issue to Jorie Tappa Puppet / PUP-3321 config set adds a preceding newline to value if previous value was empty Change By: Jorie Tappa Assignee: Jorie Tappa 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-286) Clean up Bolt::Result ExecutionResult interface
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-286 Clean up Bolt::Result ExecutionResult interface Change By: David Kramer Sprint: Bolt Ready for Grooming 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 (BOLT-286) Clean up Bolt::Result ExecutionResult interface
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-286 Clean up Bolt::Result ExecutionResult interface Change By: David Kramer Fix Version/s: BOLT 0.15.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-222) run_* functions should abort on error
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-222 run_* functions should abort on error Change By: David Kramer Sprint: Bolt Ready for Grooming 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 (BOLT-222) run_* functions should abort on error
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-222 run_* functions should abort on error Change By: David Kramer Fix Version/s: BOLT 0.15.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-222) run_* functions should abort on error
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-222
run_* functions should abort on error
Change By:
Michael Smith
h3. ProblemCurrently bolt doesn't handle errors in run_* commands well. It is left to the plan author to check for errors after each run_* actions and write error handling logic by default. This means that simple plans that call a series of run_* actions don't behave as users expect.For example the following three lines:{code}run_task(puppet_cert::clean, $caserver, host => $agent)$renew = run_task(puppet_cert::renew, [$agent], attrs => $attrs, trust_ca => $trust)run_task(puppet_cert::sign, [$caserver], 'host' => $agent, 'fingerprint' => $renew[0]['fingerprint']){code}require twice as many lines of error handling{code} $clean = run_task(puppet_cert::clean, $caserver, host => $agent)if (!$clean.ok) {util::exit("Failed to clean old certificate") } $renew = run_task(puppet_cert::renew, [$agent], attrs => $attrs, trust_ca => $trust) if(!$renew.ok) {util::exit("Failed to request new certificate") } $sign = run_task(puppet_cert::sign, [$caserver], 'host' => $agent, 'fingerprint' => $renew[0]['fingerprint']) if (!$sign.ok) {util::exit("Failed to sign new certificate") }{code}h3. SolutionThe run_* commands that return and an {{ExecutionResult}} {{run_command}} {{run_script}} {{run_task}} {{file_upload}} should by default stop execution of the plan if they error.Requirements:- When a {{run_*}} function fails execution of the plan stops by default.- Users can prevent this failure by passing {{_panic => false}} to the command(panic is a placeholder- When a plan fails because o- The CLI should print a useful method to the output stream and log at info level.*Review*{code}human:Plan aborted due to failure running #{task} on #{nodes.count} nodesExecutionResult.pretty_printjson:{ _error: { kind: "bolt/run-failure" msg: "Plan aborted due to failure running #{task} on #{nodes.count} nodes" details: {failed_targets: ["node1", "node2"]result: }} }{code}h3. Questions:What do we call the option?Can/should we do this by throwing an exception? If so what Exception class should be used?h4. Out of scopeImplementing {{_panic}} for the {{run_plan}} functionControl of
Add Comment
Jira (PUP-8336) Update for i18n support of DataHashFunctionProvider and ModuleDataProvider methods
Title: Message Title
Eric Delaney created an issue
Puppet / PUP-8336
Update for i18n support of DataHashFunctionProvider and ModuleDataProvider methods
Issue Type:
Task
Affects Versions:
PUP 5.3.3
Assignee:
Unassigned
Created:
2018/01/09 9:37 AM
Priority:
Normal
Reporter:
Eric Delaney
In the classes DataHashFunctionProvider and ModuleDataProvider, we have build a message string by using yield to get a string from a block call.
def validate_data_hash(data_hash)
...
msg = "#{yield} must use keys qualified with the name of the module"
Jira (BOLT-222) run_* functions should abort on error
Title: Message Title
David Kramer updated an issue
Puppet Task Runner / BOLT-222
run_* functions should abort on error
Change By:
David Kramer
h3. ProblemCurrently bolt doesn't handle errors in run_* commands well. It is left to the plan author to check for errors after each run_* actions and write error handling logic by default. This means that simple plans that call a series of run_* actions don't behave as users expect.For example the following three lines:{code}run_task(puppet_cert::clean, $caserver, host => $agent)$renew = run_task(puppet_cert::renew, [$agent], attrs => $attrs, trust_ca => $trust)run_task(puppet_cert::sign, [$caserver], 'host' => $agent, 'fingerprint' => $renew[0]['fingerprint']){code}require twice as many lines of error handling{code} $clean = run_task(puppet_cert::clean, $caserver, host => $agent)if (!$clean.ok) {util::exit("Failed to clean old certificate") } $renew = run_task(puppet_cert::renew, [$agent], attrs => $attrs, trust_ca => $trust) if(!$renew.ok) {util::exit("Failed to request new certificate") } $sign = run_task(puppet_cert::sign, [$caserver], 'host' => $agent, 'fingerprint' => $renew[0]['fingerprint']) if (!$sign.ok) {util::exit("Failed to sign new certificate") }{code}h3. SolutionThe run_* commands that return and {{ExecutionResult}} {{run_command}} {{run_script}} {{run_task}} {{file_upload}} should by default stop execution of the plan if they error.Requirements:- When a {{run_*}} function fails execution of the plan stops by default.- Users can prevent this failure by passing {{_panic => false}} to the command(panic is a placeholder- When a plan fails because o- The CLI should print a useful method to the output stream and log at info level.*Review*{code}human:Plan aborted due to failure running #{task} on #{nodes.count} nodesExecutionResult.pretty_printjson:{ error _error : { kind: "bolt/run-failure" msg: "Plan aborted due to failure running #{task} on #{nodes.count} nodes" details: {failed_targets: ["node1", "node2"]result: }} }{code}h3. Questions:What do we call the option?Can/should we do this by throwing an exception? If so what Exception class should be used?h4. Out of scopeImplementing {{_panic}} for the {{run_plan}} functionControl of
Add Comment
Jira (BOLT-222) run_* functions should abort on error
Title: Message Title
David Kramer updated an issue
Puppet Task Runner / BOLT-222
run_* functions should abort on error
Change By:
David Kramer
h3. ProblemCurrently bolt doesn't handle errors in run_* commands well. It is left to the plan author to check for errors after each run_* actions and write error handling logic by default. This means that simple plans that call a series of run_* actions don't behave as users expect.For example the following three lines:{code}run_task(puppet_cert::clean, $caserver, host => $agent)$renew = run_task(puppet_cert::renew, [$agent], attrs => $attrs, trust_ca => $trust)run_task(puppet_cert::sign, [$caserver], 'host' => $agent, 'fingerprint' => $renew[0]['fingerprint']){code}require twice as many lines of error handling{code} $clean = run_task(puppet_cert::clean, $caserver, host => $agent)if (!$clean.ok) {util::exit("Failed to clean old certificate") } $renew = run_task(puppet_cert::renew, [$agent], attrs => $attrs, trust_ca => $trust) if(!$renew.ok) {util::exit("Failed to request new certificate") } $sign = run_task(puppet_cert::sign, [$caserver], 'host' => $agent, 'fingerprint' => $renew[0]['fingerprint']) if (!$sign.ok) {util::exit("Failed to sign new certificate") }{code}h3. SolutionThe run_* commands that return and {{ExecutionResult}} {{run_command}} {{run_script}} {{run_task}} {{file_upload}} should by default stop execution of the plan if they error.Requirements:- When a {{run_*}} function fails execution of the plan stops by default.- Users can prevent this failure by passing {{_panic => false}} to the command(panic is a placeholder- When a plan fails in this fashion the because o- The CLI should print a useful method to the output stream and log at info level.*Review*{code}human:Plan aborted due to failure running #{task} on #{nodes.count} nodesExecutionResult.pretty_printjson:{ error: { kind: "bolt/ plan run -failure" msg: "Plan aborted due to failure running #{task} on #{nodes.count} nodes" details: {failed_targets: ["node1", "node2"]result: } } } {code}h3. Questions:What do we call the option?Can/should we do this by throwing an exception? If so what Exception class should be used?h4. Out of scopeImplementing {{_panic}} for the {{run_plan}} functionControl of
Add Comment
Jira (BOLT-300) Error Handling
Title: Message Title Yasmin Rajabi created an issue Puppet Task Runner / BOLT-300 Error Handling Issue Type: Epic Assignee: Unassigned Created: 2018/01/09 9:34 AM Priority: Normal Reporter: Yasmin Rajabi As a user its difficult to know why things aren't working because the error messaging is not clear. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-222) run_* functions should abort on error
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-222
run_* functions should abort on error
Change By:
Alex Dreyer
h3. ProblemCurrently bolt doesn't handle errors in run_* commands well. It is left to the plan author to check for errors after each run_* actions and write error handling logic by default. This means that simple plans that call a series of run_* actions don't behave as users expect.For example the following three lines:{code}run_task(puppet_cert::clean, $caserver, host => $agent)$renew = run_task(puppet_cert::renew, [$agent], attrs => $attrs, trust_ca => $trust)run_task(puppet_cert::sign, [$caserver], 'host' => $agent, 'fingerprint' => $renew[0]['fingerprint']){code}require twice as many lines of error handling{code} $clean = run_task(puppet_cert::clean, $caserver, host => $agent)if (!$clean.ok) {util::exit("Failed to clean old certificate") } $renew = run_task(puppet_cert::renew, [$agent], attrs => $attrs, trust_ca => $trust) if(!$renew.ok) {util::exit("Failed to request new certificate") } $sign = run_task(puppet_cert::sign, [$caserver], 'host' => $agent, 'fingerprint' => $renew[0]['fingerprint']) if (!$sign.ok) {util::exit("Failed to sign new certificate") }{code}h3. SolutionThe run_* commands that return and {{ExecutionResult}} {{run_command}} {{run_script}} {{run_task}} {{file_upload}} should by default stop execution of the plan if they error.Requirements:- When a {{run_*}} function fails execution of the plan stops by default.- Users can prevent this failure by passing {{_panic => false}} to the command(panic is a placeholder- When a plan fails because o- The in this fashion the CLI should print a useful method to the output stream and log at info level.*Review*{code}human:Plan aborted due to failure running #{task} on #{nodes.count} nodesExecutionResult.pretty_printjson:{ error: { kind: "bolt/plan-failure" msg: "Plan aborted due to failure running #{task} on #{nodes.count} nodes" details: {failed_targets: ["node1", "node2"]result: }{code}h3. Questions:What do we call the option?Can/should we do this by throwing an exception? If so what Exception class should be used?h4. Out of scopeImplementing {{_panic}} for the {{run_plan}} functionControl of
Add Comment
Jira (BOLT-299) Run As
Title: Message Title Yasmin Rajabi created an issue Puppet Task Runner / BOLT-299 Run As Issue Type: Epic Assignee: Unassigned Created: 2018/01/09 9:32 AM Priority: Normal Reporter: Yasmin Rajabi The run as feature allows bolt to run as another user, this epic is the grouping of the work required to complete that Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-292) Allow run_* functions to set 'run-as' value
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-292 Allow run_* functions to set 'run-as' value Change By: David Kramer Sprint: Bolt Ready for Grooming 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 (BOLT-217) Run privileged operations on Windows
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-217 Run privileged operations on Windows Change By: Michael Smith Summary: run-as support Run privileged operations on Windows 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-298) Adoption Blockers
Title: Message Title Yasmin Rajabi created an issue Puppet Task Runner / BOLT-298 Adoption Blockers Issue Type: Epic Assignee: Unassigned Created: 2018/01/09 9:30 AM Priority: Normal Reporter: Yasmin Rajabi Bolt functionality needed for additional users to adopt the tool in their workflow. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-297) Plan Output
Title: Message Title Yasmin Rajabi created an issue Puppet Task Runner / BOLT-297 Plan Output Issue Type: Epic Assignee: Unassigned Created: 2018/01/09 9:28 AM Priority: Normal Reporter: Yasmin Rajabi As a user when I am running a plan I need to be able to read the output to understand how the plan was run and what happened. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-126) Support WinRM with Kerberos
Title: Message Title Michael Smith assigned an issue to Yasmin Rajabi Puppet Task Runner / BOLT-126 Support WinRM with Kerberos Change By: Michael Smith Assignee: Michael Smith Yasmin Rajabi 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-126) Support WinRM with Kerberos
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-126 Support WinRM with Kerberos Change By: Michael Smith Bolt should have an option to use Kerberos with WinRM, such as would be found in an Active Directory domain. This enables the user to connect to remote systems without needing to specify a password (single sign-on). While there are different Kerberos implementations, I think we should focus on a simple Active Directory domain and single forest. Open question: are we trying to enable transparent login from Windows nodes in a domain to other Windows nodes in that domain, or users getting a Kerberos ticket and using it to login to Windows domain nodes from heterogeneous sources? Those are going to be completely separate to implement. 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-126) Support WinRM with Kerberos
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-126 Support WinRM with Kerberos Change By: David Kramer Sprint: Bolt Adoption Blockers 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-281) Update writing tasks doc
Title: Message Title David Kramer assigned an issue to Unassigned Puppet Task Runner / BOLT-281 Update writing tasks doc Change By: David Kramer Assignee: Michelle Fredette 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-281) Update writing tasks doc
Title: Message Title David Kramer assigned an issue to Michelle Fredette Puppet Task Runner / BOLT-281 Update writing tasks doc Change By: David Kramer Assignee: Zach Reichert Michelle Fredette 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) Uppercase class task name should not work as a reference to a task in a plan
Title: Message Title David Kramer assigned an issue to Unassigned Puppet Task Runner / BOLT-261 Uppercase class task name should not work as a reference to a task in a plan Change By: David Kramer Assignee: Lucy Wyman 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) Uppercase class task name should not work as a reference to a task in a plan
Title: Message Title David Kramer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-261 Uppercase class task name should not work as a reference to a task in a plan Change By: David Kramer Assignee: Alex Dreyer 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-8249) Certain environments return "invalid byte sequence in " when parsing module PO files
Title: Message Title Maggie Dreyer commented on PUP-8249 Re: Certain environments return "invalid byte sequence in " when parsing module PO files The maintainer of the gem has released a new version with the file read encoding backport. https://rubygems.org/gems/fast_gettext/versions/1.1.1 We now need to update our dependencies to use this (puppet gemspec, puppet-agent component, puppetserver gem list). 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-295) Run any script with extension handler on Windows
Title: Message Title David Kramer assigned an issue to Michael Smith Puppet Task Runner / BOLT-295 Run any script with extension handler on Windows Change By: David Kramer 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-8283) Puppet rejects tasks with valid non-Data types like 'Hash'
Title: Message Title David Kramer updated an issue Puppet / PUP-8283 Puppet rejects tasks with valid non-Data types like 'Hash' Change By: David Kramer Sub-team: Bolt 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-8283) Puppet rejects tasks with valid non-Data types like 'Hash'
Title: Message Title David Kramer updated an issue Puppet / PUP-8283 Puppet rejects tasks with valid non-Data types like 'Hash' Change By: David Kramer Sprint: Bolt 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-8283) Puppet rejects tasks with valid non-Data types like 'Hash'
Title: Message Title David Kramer updated an issue Puppet / PUP-8283 Puppet rejects tasks with valid non-Data types like 'Hash' Change By: David Kramer Team: Direct Change 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-8283) Puppet rejects tasks with valid non-Data types like 'Hash'
Title: Message Title David Kramer assigned an issue to Unassigned Puppet / PUP-8283 Puppet rejects tasks with valid non-Data types like 'Hash' Change By: David Kramer Assignee: Alex Dreyer 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-8123) Document that Upper case in filenames for autoloaded things like classes does not work
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-8123 Document that Upper case in filenames for autoloaded things like classes does not work Change By: Owen Rodabaugh CS Priority: Normal CS Impact: This is confusing. If we get this documented we'll have something that helps user understand the casing requirements. CS Severity: 3 - Serious CS Business Value: 3 - CS Frequency: 1 - 1-5% of Customers Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) --
Jira (PUP-8020) Add data type Target to puppet for tasks/plans
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8020 Add data type Target to puppet for tasks/plans Change By: Josh Cooper Team: 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.
