Jira (PUP-8199) Parameters in Task metadata should not collide with metadata keys
Title: Message Title Michelle Fredette updated an issue Puppet / PUP-8199 Parameters in Task metadata should not collide with metadata keys Change By: Michelle Fredette Labels: docs_reviewed 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 updated an issue
Puppet / PUP-8249
Certain environments return "invalid byte sequence in " when parsing module PO files
Change By:
Maggie Dreyer
If you load the eputnam-i18ndemo module which has a fact that causes and error that has a Japanese translation, when its run on OSX the error is replaced by "invalid byte sequence in US-ASCII"{code}xh734nh8owpuouo:~ root# puppet module install eputnam-i18ndemoNotice: Preparing to install into /etc/puppetlabs/code/environments/production/modules ...Notice: Downloading from https://forgeapi.puppet.com ...Notice: Installing -- do not interrupt .../etc/puppetlabs/code/environments/production/modules└─┬ eputnam-i18ndemo (v0.2.0) ├── puppetlabs-stdlib (v4.21.0) └── puppetlabs-translate (v1.1.0)xh734nh8owpuouo:~ root# LANGUAGE=ja_JP puppet factsError: Facter: error while resolving custom fact "i18ndemo_fact": invalid byte sequence in US-ASCII{code}Instead of the expected Japanese string (which should look like this pattern){code}assert_match(/Error:.*eputnam-i18ndemo fact: これはeputnam-i18ndemoからのカスタムファクトからのレイズです/, result.stderr, 'missing translation for raise from ruby fact'){code} This also appears, for example, on the Japanese Windows pooler image. If you install the module, then attempt to uninstall it, the uninstall will fail with a similar error, and a trace like the one in the comments.
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
Jira (PUP-8249) Certain environments return "invalid byte sequence in " when parsing module PO files
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8249 Certain environments return "invalid byte sequence in " when parsing module PO files Change By: Maggie Dreyer Sprint: Platform Core Grooming Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8249) Certain environments return "invalid byte sequence in " when parsing module PO files
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8249 Certain environments return "invalid byte sequence in " when parsing module PO files Change By: Maggie Dreyer Summary: OSX puppet facts run in japanese with facter errors returns Certain environments return "invalid byte sequence in US-ASCII " when parsing module PO files 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) OSX puppet facts run in japanese with facter errors returns "invalid byte sequence in US-ASCII"
Title: Message Title Maggie Dreyer moved an issue Puppet / PUP-8249 OSX puppet facts run in japanese with facter errors returns "invalid byte sequence in US-ASCII" Change By: Maggie Dreyer Key: FACT PUP - 1796 8249 Project: Facter Puppet 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-1796) OSX puppet facts run in japanese with facter errors returns "invalid byte sequence in US-ASCII"
Title: Message Title Maggie Dreyer commented on FACT-1796 Re: OSX puppet facts run in japanese with facter errors returns "invalid byte sequence in US-ASCII" This is not restricted to OSX, nor to the custom fact warning. It seems to appear when module PO files are parsed by fast_gettext in certain environments, including on Windows. Moving this ticket to reflect that. 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-6380) HTTP file sources fail for GET-only URIs
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-6380 HTTP file sources fail for GET-only URIs Change By: Jacob Helwig Sprint: Platform Core Grooming Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-252) Run Bolt acceptance tests on merge
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-252 Run Bolt acceptance tests on merge 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-6380) HTTP file sources fail for GET-only URIs
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-6380 HTTP file sources fail for GET-only URIs Change By: Jacob Helwig Sub-team: Coremunity 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-8248) Make systemd the default service provider for Amazon Linux 2017.12
Title: Message Title Scott Garman updated an issue Puppet / PUP-8248 Make systemd the default service provider for Amazon Linux 2017.12 Change By: Scott Garman Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 4.10.10 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8248) Make systemd the default service provider for Amazon Linux 2017.12
Title: Message Title Scott Garman moved an issue Puppet / PUP-8248 Make systemd the default service provider for Amazon Linux 2017.12 Change By: Scott Garman Key: PA PUP - 1738 8248 Project: Puppet Agent Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8131) Calls to Puppet::Util.benchmark should include a 'in %{seconds} seconds' in there message
Title: Message Title
Eric Delaney assigned an issue to Eric Delaney
Puppet / PUP-8131
Calls to Puppet::Util.benchmark should include a 'in %{seconds} seconds' in there message
Change By:
Eric Delaney
Assignee:
Eric Delaney
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8131) Calls to Puppet::Util.benchmark should include a 'in %{seconds} seconds' in there message
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-8131
Calls to Puppet::Util.benchmark should include a 'in %{seconds} seconds' in there message
Change By:
Eric Delaney
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 (PDB-3723) Use JSONB for fact storage
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3723 Use JSONB for fact storage Change By: Wyatt Alt Release Notes Summary: Replace the existing facts storage schema with a new one based on JSONB. This includes multiple benefits and some incidental new features:* Greatly improve GC performance in cases where large structured facts are updated* Improve performance of conjunction queries, for instance where users want a list of hosts with facts meeting a set of multiple criteria.* Make future development on facts querying more amenable to the type of descendence queries currently possible with the inventory endpoint* No breaking API changes 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 (BOLT-66) Run tasks through PAL so that arguments are validated
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-66 Run tasks through PAL so that arguments are validated Change By: Michelle Fredette Labels: docs_reviewed 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-66) Run tasks through PAL so that arguments are validated
Title: Message Title Michelle Fredette commented on BOLT-66 Re: Run tasks through PAL so that arguments are validated I added a new feature note for this. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3779) root endpoint queries broken for entities with no certname field
Title: Message Title Wyatt Alt commented on PDB-3779 Re: root endpoint queries broken for entities with no certname field updated Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3779) root endpoint queries broken for entities with no certname field
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3779 root endpoint queries broken for entities with no certname field Change By: Wyatt Alt Release Notes Summary: Prevent the query engine from attempting to limit queries against the v4 endpoint to active nodes in cases where the relevant entity has no certname field. In practice this makes PQL queries against fact_paths and environments work. 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 (PDB-3770) anonymization via the "puppet db export" command not working
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3770 anonymization via the "puppet db export" command not working Change By: Jeff Yarnell Sprint: Data Platform Next Sprint, Data Platform 2017-12-13 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3311) Improve error message on "index row size" exceptions
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3311 Improve error message on "index row size" exceptions Change By: Jeff Yarnell Sprint: Data Platform Next Sprint, Data Platform 2017-12-13 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3687) ordering on fact value
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3687 ordering on fact value Change By: Jeff Yarnell Sprint: Data Platform Next Sprint, Data Platform 2017-12-13 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3779) root endpoint queries broken for entities with no certname field
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3779 root endpoint queries broken for entities with no certname field Change By: Wyatt Alt Fix Version/s: PDB 5.y Fix Version/s: PDB 5.2.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 (PDB-3770) anonymization via the "puppet db export" command not working
Title: Message Title Russell Mull commented on PDB-3770 Re: anonymization via the "puppet db export" command not working AJ Roetker Any updates on this? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3779) root endpoint queries broken for entities with no certname field
Title: Message Title Russell Mull commented on PDB-3779 Re: root endpoint queries broken for entities with no certname field Wyatt Alt Can you add release notes to this? Also, I think this is PDB 5.2.0 is that right? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3723) Use JSONB for fact storage
Title: Message Title Russell Mull commented on PDB-3723 Re: Use JSONB for fact storage Wyatt Alt Can you fill in some release notes for this ticket? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3723) Use JSONB for fact storage
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3723 Use JSONB for fact storage Change By: Russell Mull Fix Version/s: PDB 5.2.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-163) Configurable connection timeout
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-163 Configurable connection timeout Change By: Michelle Fredette Labels: docs-reviewed docs_reviewed 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-147) Configure tmp dir for scripts and tasks
Title: Message Title Michelle Fredette commented on BOLT-147 Re: Configure tmp dir for scripts and tasks added a new feature note. 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-147) Configure tmp dir for scripts and tasks
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-147 Configure tmp dir for scripts and tasks Change By: Michelle Fredette Labels: docs_reviewed 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-7394) Puppet::Util.replace_file cannot be used to create a read-only file (on non-Windows)
Title: Message Title Jorie Tappa assigned an issue to Jorie Tappa Puppet / PUP-7394 Puppet::Util.replace_file cannot be used to create a read-only file (on non-Windows) 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-66) Run tasks through PAL so that arguments are validated
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-66 Run tasks through PAL so that arguments are validated Change By: Alex Dreyer Issue Type: Task New Feature Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7397) FileBucket should use `Puppet::Util::replace_file` to write contents
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-7397 FileBucket should use `Puppet::Util::replace_file` to write contents Change By: Jorie Tappa Acceptance Criteria: We should use Puppet::Util.replace_file when While uploading a large file to the server writes filebucket, attempting to retrieve a file with the contents and paths files in same hash from the filebucket should not result in partial file bucket content . This is best tested by running multiple agents and have them backup the same sets of files concurrently. You should see warnings to either get no content, in the effect of "FileBucket got case where it's a duplicate new file " and , or you should never see "Unable to verify FileBucket backup", and "Existing backup does not match its expected sum" get the complete file in the case where the file was already existing in the filebucket. 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-163) Configurable connection timeout
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-163 Configurable connection timeout Change By: Michelle Fredette Labels: docs-reviewed 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-163) Configurable connection timeout
Title: Message Title Michelle Fredette commented on BOLT-163 Re: Configurable connection timeout I added a release note. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3790) Merge 5.1.x -> master
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3790 Merge 5.1.x -> master Issue Type: Bug Assignee: Unassigned Created: 2017/12/13 1:36 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3789) Merge 4.4.x -> 5.1.x
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3789 Merge 4.4.x -> 5.1.x Issue Type: Bug Assignee: Unassigned Created: 2017/12/13 1:32 PM Priority: Normal Reporter: gepetto-bot 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-8247) Parser locator doesn't cache anything and doesn't appear to work.
Title: Message Title Josh Cooper created an issue Puppet / PUP-8247 Parser locator doesn't cache anything and doesn't appear to work. Issue Type: Task Assignee: Unassigned Created: 2017/12/13 1:29 PM Priority: Normal Reporter: Josh Cooper The Puppet::Pops::Parser::Locator attempts to cache line location information, but it ends up calling local variables prev_line etc that shadow the accessor methods of the same name. Even after fixing the code, e.g. self.prev_offset = offset self.prev_line = line_nbr The caching mechanism does not appear to work even when using unlimited environment timeouts. Given a manifest:
Jira (PUP-8247) Parser locator doesn't cache anything and doesn't appear to work.
Title: Message Title Josh Cooper assigned an issue to Henrik Lindberg Puppet / PUP-8247 Parser locator doesn't cache anything and doesn't appear to work. Change By: Josh Cooper Assignee: Henrik Lindberg 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-7397) FileBucket should use `Puppet::Util::replace_file` to write contents
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-7397 FileBucket should use `Puppet::Util::replace_file` to write contents Change By: Jorie Tappa Acceptance Criteria: We should use Puppet::Util.replace_file when the server writes the contents and paths files in the file bucket. This is best tested by running multiple agents and have them backup the same sets of files concurrently. You should see warnings to the effect of "FileBucket got a duplicate file" and you will should never see "Unable to verify FileBucket backup", and "Existing backup does not match its expected sum" 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-7397) FileBucket should use `Puppet::Util::replace_file` to write contents
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-7397 FileBucket should use `Puppet::Util::replace_file` to write contents Change By: Jorie Tappa Acceptance Criteria: We should use Puppet::Util.replace_file when the server writes the contents and paths files in the file bucket. This is best tested by running multiple agents and have them backup the same sets of files concurrently. If we are not atomically updating files, then you You should see warnings to the effect of "FileBucket got a duplicate file" and you will never see "Unable to verify FileBucket backup", and "Existing backup does not match its expected sum" 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-91) multi-task plans swallow output from all but the last task
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-91 multi-task plans swallow output from all but the last task Change By: Alex Dreyer Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-118) Oneline output format
Title: Message Title Jenny Mahmoudi commented on BOLT-118 Re: Oneline output format Remember to add labels for specific log level messages like debug and warn. 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-165) Fix plan run result output
Title: Message Title Alex Dreyer commented on BOLT-165 Re: Fix plan run result output That looks good. The format of that will probably change pretty quickly so I don't think the specific are super important. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3687) ordering on fact value
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3687 ordering on fact value Change By: Wyatt Alt Sprint: Data Platform 2017-12-13 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-114) Consider other output types like "debug", "bad"
Title: Message Title Jenny Mahmoudi commented on BOLT-114 Re: Consider other output types like "debug", "bad" If we've already got both types, then it makes sense to close this ticket. I'll add a comment to BOLT-114 about labeling those messages so we don't forget. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3702) upgrade tests broken for PDB
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3702 upgrade tests broken for PDB Change By: Jeff Yarnell Team: Data Platform Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3702) upgrade tests broken for PDB
Title: Message Title Wyatt Alt commented on PDB-3702 Re: upgrade tests broken for PDB Russell Mull Rob Browning worth not losing sight of this 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 (BOLT-114) Consider other output types like "debug", "bad"
Title: Message Title Alex Dreyer commented on BOLT-114 Re: Consider other output types like "debug", "bad" Yes we already have debug we already have "bad"(warn) which is the default too. Since we haven't done 114 why not just add a comment there about it. 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-114) Consider other output types like "debug", "bad"
Title: Message Title Jenny Mahmoudi commented on BOLT-114 Re: Consider other output types like "debug", "bad" I believe the oneline format should affect how stderr is displayed, but not what is printed to stderr. As far as this ticket goes: do we already have a debug log level? i'd like to explore the concept of labeling "bad" things in the oneline format, so I'd like to keep this ticket open. I just linked it to BOLT-114. 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-8199) Parameters in Task metadata should not collide with metadata keys
Title: Message Title
Alex Dreyer updated an issue
Puppet / PUP-8199
Parameters in Task metadata should not collide with metadata keys
Change By:
Alex Dreyer
Release Notes Summary:
This is for BoltThis fixes a bug where bolt parameter names that conflicted with top level metadata keys(parameters, input_method etc) were ignored. Breaking Change: Previously tasks were types in Puppet and the run task function could be called with a reference the Type itself or an instance of the type. With this change that is no longer the case and tasks must be referred to by their lower case task nameThe following invocations are no longer validrun_task(My_app::Deploy(), run_task(My_app::Deploy, And should be converted torun_task(my_app::deploy, ...orrun_task('my_app::deploy', ...
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-261) Quoted class task name should not work as a reference to a task in a plan
Title: Message Title
Zach Reichert created an issue
Puppet Task Runner / BOLT-261
Quoted class task name should not work as a reference to a task in a plan
Issue Type:
Bug
Affects Versions:
BOLT 0.11.0
Assignee:
Unassigned
Created:
2017/12/13 12:11 PM
Priority:
Normal
Reporter:
Zach Reichert
When I create the following plan:
plan test::my_unix_plan($nodes) {
$nodes_array = $nodes.split(',')
run_task('Test::A_unix', $nodes_array)
Jira (BOLT-114) Consider other output types like "debug", "bad"
Title: Message Title Alex Dreyer commented on BOLT-114 Re: Consider other output types like "debug", "bad" The oneline output format would control what gets printed on stdout while log messages are printed on stderr. Can I close this ticket? 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-165) Fix plan run result output
Title: Message Title
Michael Smith commented on BOLT-165
Re: Fix plan run result output
So something like
[
{
"node": "node1",
"status": "finished",
"result": {
"_output": "foo\n"
}
},
{
"node": "node2",
"status": "finished",
Jira (PDOC-194) investigate using modules to replace current script automation
Title: Message Title Randell Pelak created an issue Puppet Strings / PDOC-194 investigate using modules to replace current script automation Issue Type: Task Assignee: Unassigned Created: 2017/12/13 11:58 AM Priority: Normal Reporter: Randell Pelak 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
Jira (BOLT-114) Consider other output types like "debug", "bad"
Title: Message Title Jenny Mahmoudi commented on BOLT-114 Re: Consider other output types like "debug", "bad" Yes and no. I think this was just about offering different log levels. If we added any of these log levels, then the oneline format should label them as such, but they're not required as part of the oneline format. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3684) PDB performance issues with large structured facts
Title: Message Title Wyatt Alt commented on PDB-3684 Re: PDB performance issues with large structured facts The above has been merged. 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-165) Fix plan run result output
Title: Message Title
Michael Smith commented on BOLT-165
Re: Fix plan run result output
Should we do anything about the JSON format, or is that a different ticket?
Currently an ExecutionResult displays as
"ExecutionResult({'10-32-167-149.rfc1918.puppetlabs.net' => {'message' => 'foo'}, '10-32-167-127.rfc1918.puppetlabs.net' => {'message' => 'foo'}})"
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-66) Run tasks through PAL so that arguments are validated
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-66 Run tasks through PAL so that arguments are validated Change By: Alex Dreyer Release Notes Summary: Task paremeters are now validated when tasks are run directly with `bolt run task`. This may cause some tasks that have invalid parameter types to fail Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-147) Configure tmp dir for scripts and tasks
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-147 Configure tmp dir for scripts and tasks Change By: Alex Dreyer Release Notes Summary: The tmpdir used to upload and execute scripts and tasks is now configurable by the --tmpdir flag and transport option. This allows bolt to be used the tempdir is mounted noconfig or mktmp is not available over ssh. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-163) Configurable connection timeout
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-163 Configurable connection timeout Change By: Alex Dreyer Release Notes Summary: The timeout for connecting to ssh and winrm target can now be controller with the --connect-timeout flag or transport configuration option Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8199) Parameters in Task metadata should not collide with metadata keys
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-8199 Parameters in Task metadata should not collide with metadata keys Change By: Alex Dreyer Release Notes Summary: This is for Bolt This fixes a bug where bolt parameter names that conflicted with top level metadata keys(parameters, input_method etc) were ignored. Release Notes: Not Needed 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-8199) Parameters in Task metadata should not collide with metadata keys
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-8199 Parameters in Task metadata should not collide with metadata keys Change By: Alex Dreyer Fix Version/s: BOLT 0.11.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-66) Run tasks through PAL so that arguments are validated
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-66 Run tasks through PAL so that arguments are validated Change By: Alex Dreyer Fix Version/s: BOLT 0.11.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8246) Consolidate http client connection implementations
Title: Message Title Josh Cooper created an issue Puppet / PUP-8246 Consolidate http client connection implementations Issue Type: Task Assignee: Unassigned Created: 2017/12/13 11:24 AM Priority: Normal Reporter: Josh Cooper This ticket is a result of PUP-7482. Puppet does not allow callers to specify which CA certs should be trusted when making SSL connections (see PUP-5069). As a result, there are three places where we create SSL connections, and configure the X509::Store: 1. puppet/network/http/factory 2. puppet/util/http_proxy 3. puppet/forge/repository There are several inconsistencies as a result:
Jira (BOLT-165) Fix plan run result output
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-165 Fix plan run result output Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7482) Agent sends wrong content-type when using http file sources
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7482 Agent sends wrong content-type when using http file sources Change By: Josh Cooper Fix Version/s: PUP 5.3.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 (BOLT-260) Should be easier to pass simple types on CLI
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-260 Should be easier to pass simple types on CLI Issue Type: Improvement Assignee: Unassigned Created: 2017/12/13 11:15 AM Priority: Normal Reporter: Michael Smith A common pattern being established in plans is to pass an array of nodes. Our example at https://puppet.com/docs/bolt/0.x/writing_plans.html#defining-plan-parameters did that by passing a comma-separated list, which doesn't work at all. It's also common to want to support boolean and integer types, which currently also require falling back to passing a JSON blob. We should detect the types required by a task or plan and try to coerce command-line arguments to those types when unambiguous, to avoid making people pass JSON all the time. One challenging example of this is from our plan docs: Variant[String[1], Array[String[1]]] $backends with a CLI arg of backends=kermit.myorg.com,gonzo.myorg.com could either be a string, or an array of 2 items. Also backends=kermit.myorg.com could be a string or an array of 1 item. We'll need to decide how to handle that. Add Comment
Jira (BOLT-260) Should be easier to pass simple types on CLI
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-260 Should be easier to pass simple types on CLI Change By: Michael Smith Sub-team: Bolt Team: Direct Change 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-259) Config file should use .yaml extension
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-259 Config file should use .yaml extension Issue Type: Improvement Assignee: Unassigned Created: 2017/12/13 11:10 AM Priority: Normal Reporter: Michael Smith Other tools in the Puppet ecosystem use the .yaml extension rather than .yml. We should do the same for the default config file to be more consistent. Bonus-points for accepting .yaml and .yml? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-258) Configuration options for the PCP transport
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-258 Configuration options for the PCP transport Change By: Alex Dreyer 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 (BOLT-258) Configuration options for the PCP transport
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-258
Configuration options for the PCP transport
Change By:
Alex Dreyer
The orchestrator pcp transport should be configurable from the bolt configuration file. example {code} pcp: service-url: cacert: token-file: environment:{code}service-url, cacert and token-file should be passed to the OrchestratorClient when it's created. If they are nil or not present they should not passed so defaults in the client library can be used.environment should be passed added to the task command body.User story for environment When a customer's primary environment (or environment relevant to a set of tasks) is ≠ production, it is impossible today to use Bolt and transport=pcp to run a plan using those tasks. Users should be able to configure what environment is sent to orchestrator as part of the task command with the {{task-environment}} configuration option in the pcp section of bolt.yml
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3788) (maint) Add build_tar: FALSE to build_defaults
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3788 (maint) Add build_tar: FALSE to build_defaults Issue Type: Bug Assignee: Unassigned Created: 2017/12/13 10:44 AM Priority: Normal Reporter: gepetto-bot Our automation is attempting to sign tarballs that aren't there. This will make sure we don't try to do that. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PDB-3787) (maint) Update packaging.sh file to reflect change to artifactory
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3787 (maint) Update packaging.sh file to reflect change to artifactory Issue Type: Bug Assignee: Unassigned Created: 2017/12/13 10:43 AM Priority: Normal Reporter: gepetto-bot We are making the change from nexus to artifactory Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PDB-3786) (maint) Add build_tar: FALSE to build_defaults
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3786 (maint) Add build_tar: FALSE to build_defaults Issue Type: Bug Assignee: Unassigned Created: 2017/12/13 10:40 AM Priority: Normal Reporter: gepetto-bot Our automation is attempting to sign tarballs that aren't there. This will make sure we don't try to do that. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PDB-3785) (maint) Update packaging.sh file to reflect change to artifactory
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3785 (maint) Update packaging.sh file to reflect change to artifactory Issue Type: Bug Assignee: Unassigned Created: 2017/12/13 10:39 AM Priority: Normal Reporter: gepetto-bot We are making the change from nexus to artifactory. [tested here](https://artifactory.delivery.puppetlabs.net/artifactory/list/clojure-snapshots__local/puppetlabs/pe-puppetdb-extensions/4.4.3-SNAPSHOT/) Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-3963) Error message gives wrong advice for allowed module names
Title: Message Title Melissa Stone updated an issue Puppet / PUP-3963 Error message gives wrong advice for allowed module names Change By: Melissa Stone Sub-team: Coremunity 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 (BOLT-258) Configuration options for the PCP transport
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-258 Configuration options for the PCP transport Change By: Alex Dreyer Summary: When using Configuration options for the PCP transport =pcp, should be possible to specify environment Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-258) Configuration options for the PCP transport
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-258
Configuration options for the PCP transport
Change By:
Alex Dreyer
When a customer's primary environment (or environment relevant to a set of tasks) is ≠ production, it is impossible today to use Bolt and transport=pcp to run a plan using those tasks. Users should be able to configure what environment is sent to orchestrator as part of the task command with the {{task-environment}} configuration option in the pcp section of bolt.yml
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3784) (maint) Update packaging.sh file to reflect change to artifactory
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3784 (maint) Update packaging.sh file to reflect change to artifactory Issue Type: Bug Assignee: Unassigned Created: 2017/12/13 10:36 AM Priority: Normal Reporter: gepetto-bot We are making the change from nexus to artifactory Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-114) Consider other output types like "debug", "bad"
Title: Message Title Alex Dreyer commented on BOLT-114 Re: Consider other output types like "debug", "bad" @jenny is this part of the oneline output? 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 Josh Cooper updated an issue Puppet / PUP-7482 Agent sends wrong content-type when using http file sources Change By: Josh Cooper Summary: Error when downloading file hosted in IIS (mime Agent sends wrong content -type issue?) when using http file sources 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) Error when downloading file hosted in IIS (mime-type issue?)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7482 Error when downloading file hosted in IIS (mime-type issue?) Change By: Josh Cooper Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-258) When using transport=pcp, should be possible to specify environment
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-258 When using transport=pcp, should be possible to specify environment As part of this we probably need to allow the other orchestrator config options to be configured through the config file: token-path cacert service-uri Change By: Alex Dreyer Sub-team: Bolt Team: Direct Change 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) Error when downloading file hosted in IIS (mime-type issue?)
Title: Message Title Josh Cooper commented on PUP-7482 Re: Error when downloading file hosted in IIS (mime-type issue?) Thanks Eric. So the problem is the code path for downloading file content via http bypasses our normal http connection code and sets a non-standard binary content-type. IIS is rejecting it with HTTP 406 as expected. There is a simple fix we can do now, which is to use the correct application/octet-stream content type. I'll file a separate ticket to reconcile the two implementations, because we're not using persistent connections when sourcing files from http, not sending User-Agent, and other normal puppet HTTP headers. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-258) When using transport=pcp, should be possible to specify environment
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-258
When using transport=pcp, should be possible to specify environment
Change By:
Alex Dreyer
When a customer's primary environment (or environment relevant to a set of tasks) is ≠ production, it is impossible today to use Bolt and transport=pcp to run a plan using those tasks. What we have: Users should be able to configure what environment is sent to orchestrator as part of the task command with the { code}bolt plan run --transport=pcp { code}What we need:{code}bolt plan run task - -transport=pcp -- environment =iac_production{code } This support could come } configuration option in the form pcp section of a CLI flag, or a configuration file option bolt . Either would provide for the basic use case. Both would be desirable to have. yml
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-258) When using transport=pcp, should be possible to specify environment
Title: Message Title
Reid Vandewiele updated an issue
Puppet Task Runner / BOLT-258
When using transport=pcp, should be possible to specify environment
Change By:
Reid Vandewiele
When a customer's primary environment (or environment relevant to a set of tasks) is ≠ production, it is impossible today to use Bolt and transport=pcp to run a plan using those tasks.What we have:{code}bolt plan run --transport = pcp{code}What we need:{code } bolt plan run --transport = pcp --environment = iac_production{code}This support could come in the form of a CLI flag, or a configuration file option. Either would provide for the basic use case. Both would be desirable to have.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-258) When using transport=pcp, should be possible to specify environment
Title: Message Title
Reid Vandewiele updated an issue
Puppet Task Runner / BOLT-258
When using transport=pcp, should be possible to specify environment
Change By:
Reid Vandewiele
When a customer's primary environment (or environment relevant to a set of tasks) is ≠ production, it is impossible today to use Bolt and transport=pcp to run a plan using those tasks.What we have:{code}bolt plan run --transport = pcp{code}What we need:{codebolt plan run --transport = pcp --environment = iac_production{code}This support could come in the form of a CLI flag, or a configuration file option. Either would provide for the basic use case. Both would be desirable to have.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-258) When using transport=pcp, should be possible to specify environment
Title: Message Title
Reid Vandewiele created an issue
Puppet Task Runner / BOLT-258
When using transport=pcp, should be possible to specify environment
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2017/12/13 10:13 AM
Priority:
Normal
Reporter:
Reid Vandewiele
When a customer's primary environment (or environment relevant to a set of tasks) is ≠ production, it is impossible today to use Bolt and transport=pcp to run a plan using those tasks.
What we have:
bolt plan run --transport=pcp
What we need: {code bolt plan run --transport=pcp --environment=iac_production
Jira (BOLT-257) Plan docs are totally broken
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-257
Plan docs are totally broken
Change By:
Michael Smith
https://puppet.com/docs/bolt/0.x/writing_plans.html#defining-plan-parameters doesn't work at all. Should be updated to: I'll update the description with what should go there once I get something working. {code}You can specify parameters in your plan.Specify each parameter in your plan with its data type. For example, you might want parameters to specify which nodes to run different parts of your plan on.The following example shows node parameters specified as data type `Variant[String[1], Array[String[1]]]`. For more information about these data types, see the common data types table in the related metadata type topic.This allows the user to pass, for each parameter, either a simple node name or a URI that describes the protocol to use, the hostname, username and password.The plan then calls the run_task function, specifying which nodes the tasks should be run on.```plan mymodule::my_plan( String[1]$load_balancer, Variant[String[1], Array[String[1]]] $frontends, Variant[String[1], Array[String[1]]] $backends,) { # process frontends run_task('mymodule::lb_remove', $load_balancer, frontends => $frontends) run_task('mymodule::update_frontend_app', $frontends, version => '1.2.3') run_task('mymodule::lb_add', $load_balancer, frontends => $frontends)} ```To execute this plan from the command line, pass the parameters as parameter=value:```bolt plan run mymodule::myplan --modules ./PATH/TO/MODULES --params '{"load_balancer":"lb.myorg.com","frontends":["kermit.myorg.com","gonzo.myorg.com"],"backends":["waldorf.myorg.com","statler.myorg.com"]}'```{code}Types were all missing a trailing square bracket, and the way parameters were passed doesn't work yet.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-256) Bolt plan printing gets null plan with simple example
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-256 Bolt plan printing gets null plan with simple example Change By: Michael Smith Attachment: echo.tgz 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-257) Plan docs are totally broken
Title: Message Title Michael Smith assigned an issue to Michelle Fredette Puppet Task Runner / BOLT-257 Plan docs are totally broken Change By: Michael Smith 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-257) Plan docs are totally broken
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-257
Plan docs are totally broken
Change By:
Michael Smith
https://puppet.com/docs/bolt/0.x/writing_plans.html#defining-plan-parameters doesn't work at all.I'll update the description with what should go there once I get something working. {code}You can specify parameters in your plan.Specify each parameter in your plan with its data type. For example, you might want parameters to specify which nodes to run different parts of your plan on.The following example shows node parameters specified as data type `Variant[String[1], Array[String[1]]]`. For more information about these data types, see the common data types table in the related metadata type topic.This allows the user to pass, for each parameter, either a simple node name or a URI that describes the protocol to use, the hostname, username and password.The plan then calls the run_task function, specifying which nodes the tasks should be run on.```plan mymodule::my_plan( String[1]$load_balancer, Variant[String[1], Array[String[1]]] $frontends, Variant[String[1], Array[String[1]]] $backends,) { # process frontends run_task('mymodule::lb_remove', $load_balancer, frontends => $frontends) run_task('mymodule::update_frontend_app', $frontends, version => '1.2.3') run_task('mymodule::lb_add', $load_balancer, frontends => $frontends)} ```To execute this plan from the command line, pass the parameters as parameter=value:```bolt plan run mymodule::myplan --modules ./PATH/TO/MODULES --params '{"load_balancer":"lb.myorg.com","frontends":["kermit.myorg.com","gonzo.myorg.com"],"backends":["waldorf.myorg.com","statler.myorg.com"]}'```{code}Types were all missing a trailing square bracket, and the way parameters were passed doesn't work yet.
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-257) Plan docs are totally broken
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-257 Plan docs are totally broken Issue Type: Bug Assignee: Unassigned Components: DOCS Created: 2017/12/13 10:09 AM Priority: Normal Reporter: Michael Smith https://puppet.com/docs/bolt/0.x/writing_plans.html#defining-plan-parameters doesn't work at all. I'll update the description with what should go there once I get something working. Add Comment
Jira (BOLT-256) Bolt plan printing gets null plan with simple example
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-256 Bolt plan printing gets null plan with simple example Issue Type: Bug Assignee: Unassigned Created: 2017/12/13 10:07 AM Priority: Normal Reporter: Michael Smith Using the attached module - based on https://puppet.com/docs/bolt/0.x/writing_plans.html#defining-plan-parameters - run be bolt plan run echo::foo nodes=foo,bar --modulepath ... I get NoMethodError: undefined method `module_for_type' for nil:NilClass /bolt/vendored/puppet/lib/puppet/pops/types/p_object_type_extension.rb:27:in `create'
Jira (PUP-7482) Error when downloading file hosted in IIS (mime-type issue?)
Title: Message Title Eric commented on PUP-7482 Re: Error when downloading file hosted in IIS (mime-type issue?) Version proof, root@eh-ubuntu16-prod106:/tmp# puppet --version 5.3.3 root@eh-ubuntu16-prod106:/tmp# Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8106) "mount" type should autorequire its mountpoint
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8106 "mount" type should autorequire its mountpoint Change By: Melissa Stone Labels: community Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8106) "mount" type should autorequire its mountpoint
Title: Message Title Melissa Stone updated an issue Puppet / PUP-8106 "mount" type should autorequire its mountpoint Change By: Melissa Stone Sub-team: Coremunity 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-163) Configurable connection timeout
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-163 Configurable connection timeout Change By: David Kramer Fix Version/s: BOLT 0.11.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8236) drop feature branch from github
Title: Message Title Alex Dreyer assigned an issue to Unassigned Puppet / PUP-8236 drop feature branch from github Change By: Alex Dreyer 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-8236) drop feature branch from github
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8236 drop feature branch from github Change By: Henrik Lindberg 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.
