Jira (HI-577) Standalone `hiera` command errors with hiera v5 config file
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-577 Standalone `hiera` command errors with hiera v5 config file Change By: Henrik Lindberg Release Notes Summary: The standalone and deprecated `hiera` CLI does not work with hiera version 5. Please use the `lookup` CLI instead as it works with hiera versions 3, 4 and 5. Release Notes: Bug Fix Known Issue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-577) Document that standalone `hiera` CLI does not support hiera v5 config file (errors)
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-577 Document that standalone `hiera` CLI does not support hiera v5 config file (errors) Change By: Henrik Lindberg Summary: Standalone Document that standalone `hiera` command errors with CLI does not support hiera v5 config file (errors) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-577) Document that standalone `hiera` CLI does not support hiera v5 config file (errors)
Title: Message Title Garrett Guillotte updated an issue Hiera / HI-577 Document that standalone `hiera` CLI does not support hiera v5 config file (errors) Change By: Garrett Guillotte Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-604) CLONE - Document that standalone `hiera` CLI does not support hiera v5 config file (errors)
Title: Message Title Geoff Williams created an issue Hiera / HI-604 CLONE - Document that standalone `hiera` CLI does not support hiera v5 config file (errors) Issue Type: Bug Assignee: Garrett Guillotte Components: DOCS Created: 2018/06/19 7:28 AM Environment: RHEL7 $ which hiera /opt/puppetlabs/bin/hiera ]$ hiera --version 3.3.2 $ rpm -qf /opt/puppetlabs/bin/hiera puppet-agent-1.10.5-1.el7.x86_64 Priority: Normal Reporter: Geoff Williams Overview Sometimes you need to use the standalone hiera command to debug a hierarchy when working with tools such as onceover or when setting up a whole puppet lookup environment is impractical. If this is attempted using the hiera command shipped in puppet-agent-1.10.5-1.el7.x86_64.rpm user will always encounter a confusing error if version is set to > 3 in the hiera.yaml file Expected result Expect to be able to lookup data item on the command line using hiera command and hiera v5 config file Actual result User receives the error: Failed to start Hiera: RuntimeError: v4 hiera.yaml is only to be used inside an environment or a module and cannot be given to the global hiera Steps to reporoduce 1. Hiera.yaml
Jira (PUP-8726) Agent Functions - Content negotiation of rich data types to old/new agents
Title: Message Title Henrik Lindberg assigned an issue to Josh Cooper Puppet / PUP-8726 Agent Functions - Content negotiation of rich data types to old/new agents Change By: Henrik Lindberg Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8947) Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type
Title: Message Title Henrik Lindberg commented on PUP-8947 Re: Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type Doing this for APL only would be simpler since classes only have a single signature. (i.e. passing values have to use the right data type, converting to Sensitive would only be made for values that are looked up). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3940) Investigate clojure 1.9 support
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3940 Investigate clojure 1.9 support Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8949) Package pip provide won't work with ensure latest and custom index
Title: Message Title
Anton Fomenko created an issue
Puppet / PUP-8949
Package pip provide won't work with ensure latest and custom index
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/06/19 8:45 AM
Priority:
Normal
Reporter:
Anton Fomenko
Puppet agent will run every time if you have ensure => latest and custom index, for example
package { 'mypippackage':
ensure => latest,
provider=> 'pip',
install_options => { '--index' => 'https://pip.example.com' },
}
I believe the issue is happening because puppet doesn't test package version against additional index (doesn;t use --index), while using --index on install.
Jira (BOLT-604) Kick off release pipeline (Bolt 0.21.0)
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-604 Kick off release pipeline (Bolt 0.21.0) Issue Type: Sub-task Assignee: Lucy Wyman Created: 2018/06/19 8:56 AM Due Date: 2018/06/19 Priority: Normal Reporter: Lucy Wyman (Initial planned release date: 2018-06-19) With our shiny new automated builds pipeline, all you have to do is Go to https://jenkins-master-prod-1.delivery.puppetlabs.net/view/bolt/job/platform_bolt-vanagon_bolt-release-init_bolt-release/ Click "Build with Parameters" Check the PUBLIC checkbox Enter the version in the NEW_TAG box (x.y.z format) Click build! And make sure the pipeline is green! Add Comment
Jira (BOLT-607) Send release announcements (Bolt 0.21.0)
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-607 Send release announcements (Bolt 0.21.0) Issue Type: Sub-task Assignee: Kate Lopresti Created: 2018/06/19 8:56 AM Due Date: 2018/06/19 Priority: Normal Reporter: Lucy Wyman (Initial planned release date: 2018-06-19) Once docs have finished building (check that all links resolve appropriately) - Send the announcement pasted by Kate Lopresti to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and d...@puppet.com (all separately). You must be a member of these groups in order to send. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. If you want, make a PSA on IRC and/or Slack, something along the lines of "PSA: Bolt 0.21.0 is now available". Add Comment
Jira (PDB-3930) PQL's ~ matches incorrectly on dotted variables
Title: Message Title Adam Bottchen updated an issue PuppetDB / PDB-3930 PQL's ~ matches incorrectly on dotted variables Change By: Adam Bottchen CS Priority: Reviewed CS Impact: CS Triage feedback on this issue is available in PE-24298. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-603) Reconcile git commits, JIRA tickets, and versions (Bolt 0.21.0)
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-603 Reconcile git commits, JIRA tickets, and versions (Bolt 0.21.0) Issue Type: Sub-task Assignee: Lucy Wyman Created: 2018/06/19 8:56 AM Due Date: 2018/06/19 Priority: Normal Reporter: Lucy Wyman (Initial planned release date: 2018-06-19) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=Bolt and fixVersion="Bolt x.y.z"' in JIRA. Add Comment
Jira (BOLT-602) Bolt 0.21.0 2018-06-19 Release
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-602 Bolt 0.21.0 2018-06-19 Release Issue Type: Task Assignee: Lucy Wyman Created: 2018/06/19 8:56 AM Priority: Normal Reporter: Lucy Wyman Bolt 0.21.0 2018-06-19 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-605) Update homebrew-puppet (Bolt 0.21.0)
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-605 Update homebrew-puppet (Bolt 0.21.0) Issue Type: Sub-task Assignee: Lucy Wyman Created: 2018/06/19 8:56 AM Due Date: 2018/06/19 Priority: Normal Reporter: Lucy Wyman (Initial planned release date: 2018-06-19) Until we automate this, you'll also need to update the version and SHA hashes of https://github.com/puppetlabs/homebrew-puppet/blob/master/Casks/puppet-bolt.rb. To do this please Create a fork of the homebrew-puppet repo Create a new branch on that fork Update the version to the new version in https://github.com/puppetlabs/homebrew-puppet/blob/master/Casks/puppet-bolt.rb Download the `puppet-bolt-latest.dmg` from http://downloads.puppetlabs.com/mac/10.13/PC1/x86_64/, http://downloads.puppetlabs.com/mac/10.12/PC1/x86_64/, and http://downloads.puppetlabs.com/mac/10.11/PC1/x86_64/ Calculate the SHA256 hash of each `.dmg` package by running `shasum -a 256 ` Update the sha hashes in the file linked above Put up a PR to homebrew-puppet and request review
Jira (BOLT-606) Docs for bolt release (Bolt 0.21.0)
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-606 Docs for bolt release (Bolt 0.21.0) Issue Type: Sub-task Assignee: Kate Lopresti Created: 2018/06/19 8:56 AM Due Date: 2018/06/19 Priority: Normal Reporter: Lucy Wyman (Initial planned release date: 2018-06-19) Release notes and docs changes for bolt 0.21.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-602) Bolt 0.21.0 2018-06-19 Release
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-602 Bolt 0.21.0 2018-06-19 Release Change By: Lucy Wyman Team: Direct Change Bolt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-602) Bolt 0.21.0 2018-06-19 Release
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-602 Bolt 0.21.0 2018-06-19 Release Change By: Lucy Wyman Sub-team: Bolt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-503) Use local config automatically to embed bolt in a project
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-503 Use local config automatically to embed bolt in a project Change By: David Kramer Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-602) Bolt 0.21.0 2018-06-19 Release
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-602 Bolt 0.21.0 2018-06-19 Release Change By: Lucy Wyman Sprint: Bolt Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-579) I want to know what output format bolt is using
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-579 I want to know what output format bolt is using Change By: David Kramer Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-601) Demonstrate deploying higher-level resources in plans
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-601 Demonstrate deploying higher-level resources in plans Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-581) Evaluate top 100 modules
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-581 Evaluate top 100 modules Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-523) I want to install modules with bolt
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-523 I want to install modules with bolt Change By: David Kramer Currently bolt does not ship with any tool to install modules. This means users need to install the puppet agent package or r10k into some ruby (we don't make it easy to install into bolts). This is especially a problem for users getting started with bolt who quickly have to find, install and use a completely different tool.Assumptions: 1. pmt is too broken an unmaintained to add support for 2. Puppetfile based installations are good enough for users getting started if we point them at a basic control repo (task-modules) 3. Bolt users do not need the sort of global configuration of a remote control repo and syncing of multiple branches that makes sense on a puppet master. 4. r10k is cryptic a cryptic command name and should be hidden from new users.Solution: Bolt should be packaged with the r10k gem but not expose the r10k command Bolt should expose a command to install modules from a puppetfile such that downloading a control repo and installing locally is easy. Bolt should use a puppetfile from the Boltdir and install into the Boltdir when in Boltdir mode. Questions: What should Examples of invoking the command be? : `bolt puppetfile install` `bolt puppetfile install --boltdir=.` Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-523) I want to install modules with bolt
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-523 I want to install modules with bolt Change By: David Kramer Currently bolt does not ship with any tool to install modules. This means users need to install the puppet agent package or r10k into some ruby (we don't make it easy to install into bolts). This is especially a problem for users getting started with bolt who quickly have to find, install and use a completely different tool.Assumptions: 1. pmt is too broken an unmaintained to add support for 2. Puppetfile based installations are good enough for users getting started if we point them at a basic control repo (task-modules) 3. Bolt users do not need the sort of global configuration of a remote control repo and syncing of multiple branches that makes sense on a puppet master. 4. r10k is cryptic a cryptic command name and should be hidden from new users.Solution: Bolt should be packaged with the r10k gem but not expose the r10k command Bolt should expose a command to install modules from a puppetfile such that downloading a control repo and installing locally is easy. Bolt should use a puppetfile from the Boltdir and install into the Boltdir when in Boltdir mode.Questions: What should the command be? `bolt puppetfile install` `bolt puppetfile install --boltdir=.` Should bolt become more opinionated on where code lives outside of the context of a boltdir? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-523) I want to install modules with bolt
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-523 I want to install modules with bolt Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-523) I want to install modules with bolt
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-523 I want to install modules with bolt Change By: David Kramer Currently bolt does not ship with any tool to install modules. This means users need to install the puppet agent package or r10k into some ruby (we don't make it easy to install into bolts). This is especially a problem for users getting started with bolt who quickly have to find, install and use a completely different tool.Assumptions: 1. pmt is too broken an unmaintained to add support for 2. Puppetfile based installations are good enough for users getting started if we point them at a basic control repo (task-modules) 3. Bolt users do not need the sort of global configuration of a remote control repo and syncing of multiple branches that makes sense on a puppet master. 4. r10k is cryptic a cryptic command name and should be hidden from new users.Solution: Bolt should be packaged with the r10k gem but not expose the r10k command Bolt should expose a command to install modules from a puppetfile such that downloading a control repo and installing locally is easy. Bolt should use a puppetfile from the Boltdir and install into the Boltdir when in Boltdir mode.Examples of invoking the command: `bolt puppetfile install` `bolt puppetfile install --boltdir=.` The hands-on lab also needs to be updated to include puppetfiles and the instructions updated to use the `bolt puppetfile install` command. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-601) Demonstrate deploying higher-level resources in plans
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-601 Demonstrate deploying higher-level resources in plans Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-592) Running Bolt task in CI to non-localhost fails
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-592 Running Bolt task in CI to non-localhost fails Change By: David Kramer Sprint: Bolt Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-568) POC task or plan to apply POC catalogs
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-568 POC task or plan to apply POC catalogs Change By: David Kramer To complete our end to end workflow and validate the catalogs produced we should create a task or plan that applies the catalog on a target nodeRequirements:Accepts a catalog and target as inputApplies catalogSupplies some form of reportOut of scope:any pluginsync or module installation on the target. All modules must already be on the modulepath This is not blocked on BOLT-567. Progress can be made on this using a small catalog with only inline file content. QuestionsIs there work we will have to do to run reportsWhat will code distribution look like? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group
Jira (BOLT-594) POC apply keyword
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-594
POC apply keyword
Change By:
Michael Smith
We should create a POC of the apply keyword that uses the POC catalog compiler and POC catalog applicator task.In scope:It should error if called inside another apply.It should handle core types.It should use the vars and facts from the target object for the scope.Support the following plan on centos7 nodes over ssh:{noformat}plan simple (TargetSpec $nodes) { run_plan('facts', $nodes) apply($nodes) {file { "/root/test/": ensure => directory,} -> file { '/root/test/hello.txt': ensure => file, content => "hi there I'm ${$facts['os']['family'] } \n",} }}{noformat}Out of scope:File sourcesReturning a meaningful resulthandling any arguments other than targethandling errors from the compiler cleanlypassing the current scope of the plan to the compilerany fact discovery magic.Questions Where should this code land? A feature branch of puppet?
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-568) POC task or plan to apply POC catalogs
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-568 POC task or plan to apply POC catalogs Change By: David Kramer To complete our end to end workflow and validate the catalogs produced we should create a task or plan that applies the catalog on a target nodeRequirements: Accepts a catalog and target as input Applies catalog Supplies some form of reportOut of scope: any pluginsync or module installation on the target. All modules must already be on the modulepathThis is not blocked on BOLT-567. Progress can be made on this using a small catalog with only inline file content.Questions to be answered by working this ticket: * Is there work we will have to do to run reports ? * What will code distribution look like? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs
Jira (BOLT-568) POC task or plan to apply POC catalogs
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-568 POC task or plan to apply POC catalogs Change By: David Kramer To complete our end to end workflow and validate the catalogs produced we should create a task or plan that applies the catalog on a target nodeRequirements: Accepts a catalog and target as input Applies catalog Supplies some form of reportOut of scope: any pluginsync or module installation on the target. All modules must already be on the modulepathThis is not blocked on BOLT-567. Progress can be made on this using a small catalog with only inline file content.Questions to be answered by working this ticket: Is there work we will have to do to run reports What will code distribution look like? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubs
Jira (BOLT-568) POC task or plan to apply POC catalogs
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-568
POC task or plan to apply POC catalogs
Change By:
Alex Dreyer
To complete our end to end workflow and validate the catalogs produced we should create a task or plan that applies the catalog on a target nodeRequirements: Accepts a catalog and target as input Applies catalog Supplies some form of report Manifest to use for poc catalog{noformat}file { "/root/test/": ensure => directory,} -> file { '/root/test/hello.txt':ensure => file,content => "hi there I'm ${$facts['os']['family']\n",}{noformat} Out of scope: any pluginsync or module installation on the target. All modules must already be on the modulepathThis is not blocked on BOLT-567. Progress can be made on this using a small catalog with only inline file content.Questions to be answered by working this ticket: * Is there work we will have to do to generate run reports ? * What will code distribution look like?
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-568) POC task or plan to apply POC catalogs
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-568 POC task or plan to apply POC catalogs Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7141) Refactor required string dup in 3x runtime converter
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-7141 Refactor required string dup in 3x runtime converter Change By: Maggie Dreyer Labels: Language Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8716) Remove puppet module generate functionality
Title: Message Title Jacob Helwig commented on PUP-8716 Re: Remove puppet module generate functionality Merged to master branch in 4fc6125180. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-583) Unable to use "localhost" as a node on Windows
Title: Message Title
David Kramer updated an issue
Puppet Task Runner / BOLT-583
Unable to use "localhost" as a node on Windows
Change By:
David Kramer
When running a PowerShell task on a local computer with a correctly configured WinRM service, but with the target node of 'localhost' I get a message saying it's not supported and really obtuse error stack.Using a simple trick of {{--nodes '127.0.0.1'}} works around the issue.Note - The IP6 loopback {{::1}} does not workexample {code} C:\Source\puppetlabs-wsus_client [(f2ade67...) +1 ~0 -0 !]> bolt task run wsus_client::update_history --modulepath .\spec\fixtures\modules\ --nodes localhost --transport winrm --no-ssl --user --passwordPlease enter your password:C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/transport/local.rb:24:in `initialize': The local transport is not yet implemented on Windows (NotImplementedError)from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:25:in `new'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:25:in `block (2 levels) in initialize'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/delay.rb:87:in `block in value'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `block in synchronize'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `synchronize'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `synchronize'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/delay.rb:83:in `value'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/delay.rb:135:in `wait'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/concern/obligation.rb:87:in `wait!'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:39:in `transport'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:52:in `block in batch_execute'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:51:in `each'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:51:in `flat_map'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:51:in `batch_execute'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:161:in `block in run_task'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/
Jira (BOLT-583) Unable to use "localhost" as a node on Windows
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-583 Unable to use "localhost" as a node on Windows Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-594) POC apply keyword
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-594 POC apply keyword Change By: David Kramer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-594) POC apply keyword
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-594
POC apply keyword
Change By:
Michael Smith
We should create a POC of the apply keyword that uses the POC catalog compiler and POC catalog applicator task.In scope:It should error if called inside another apply.It should handle core types.It should use the vars and facts from the target object for the scope.Support the following plan on centos7 nodes over ssh:{noformat}plan simple (TargetSpec $nodes) { run_plan('facts', $nodes) apply($nodes) {file { "/root/test/": ensure => directory,} -> file { '/root/test/hello.txt': ensure => file, content => "hi there I'm ${$facts['os']['family']}\n",} }}{noformat}Out of scope:File sourcesReturning a meaningful resulthandling any arguments other than targethandling errors from the compiler cleanlypassing the current scope of the plan to the compilerany fact discovery magic.Questions Where should this code land? A feature branch of puppet? This makes sense on a feature branch of Puppet, those are still low-cost to use.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-594) POC apply keyword
Title: Message Title Michael Smith commented on BOLT-594 Re: POC apply keyword Puppet should handle compiling the body of the apply keyword to an AST and scope, then hand those off to Bolt (via a global scope lookup like Puppet.lookup(:bolt_executor)). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-608) Support local transport on windows
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-608 Support local transport on windows Issue Type: New Feature Assignee: Unassigned Created: 2018/06/19 10:05 AM Priority: Normal Reporter: Alex Dreyer Bolt should support the local transport on windows In scope: Refactor winrm transport to make powershell snippets and executable discovery reusable. Run .ps tasks in powershell locally from ruby Run other tasks based on the configured executables for the local transport Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-583) Unable to use "localhost" as a node on Windows
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-583
Unable to use "localhost" as a node on Windows
Change By:
Alex Dreyer
When running a PowerShell task on a local computer with a correctly configured WinRM service, but with the target node of 'localhost' I get a message saying it's not supported and really obtuse error stack.Using a simple trick of {{--nodes '127.0.0.1'}} works around the issue.Note - The IP6 loopback {{::1}} does not workexample{code}C:\Source\puppetlabs-wsus_client [(f2ade67...) +1 ~0 -0 !]> bolt task run wsus_client::update_history --modulepath .\spec\fixtures\modules\ --nodes localhost --transport winrm --no-ssl --user --passwordPlease enter your password:C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/transport/local.rb:24:in `initialize': The local transport is not yet implemented on Windows (NotImplementedError)from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:25:in `new'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:25:in `block (2 levels) in initialize'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/delay.rb:87:in `block in value'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `block in synchronize'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `synchronize'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/synchronization/mri_lockable_object.rb:38:in `synchronize'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/delay.rb:83:in `value'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/delay.rb:135:in `wait'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/concurrent-ruby-1.0.5/lib/concurrent/concern/obligation.rb:87:in `wait!'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:39:in `transport'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:52:in `block in batch_execute'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:51:in `each'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:51:in `flat_map'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:51:in `batch_execute'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.4.0/gems/bolt-0.20.5/lib/bolt/executor.rb:161:in `block in run_task'from C:/Program Files/Puppet Labs/Bolt/lib/ruby/gems/2.
Jira (PDB-3652) Throw cli-errors trapperkeeper will actually recognize
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-3652 Throw cli-errors trapperkeeper will actually recognize Change By: Zachary Kent Assignee: Zachary Kent Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3702) upgrade tests broken for PDB
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-3702 upgrade tests broken for PDB Change By: Zachary Kent Assignee: Zachary Kent Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8950) Fix external_ca_support tests in puppet server master
Title: Message Title Justin Stoller moved an issue Puppet / PUP-8950 Fix external_ca_support tests in puppet server master Change By: Justin Stoller Fix Version/s: None Key: SERVER PUP - 2234 8950 Project: Puppet Server Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-609) I want to filter targets from my inventory based on facts
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-609 I want to filter targets from my inventory based on facts Issue Type: Story Assignee: Unassigned Created: 2018/06/19 1:05 PM Priority: Normal Reporter: Alex Dreyer My inventory has facts associated with targets(either from a static yaml file or a fact gathering plan). I want to target a group of nodes based on filtering rules on the facts. Questions? how are queries structured? A lambda, A pql string? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-592) Running Bolt task in CI to non-localhost fails
Title: Message Title Nick Walker commented on BOLT-592 Re: Running Bolt task in CI to non-localhost fails Yasmin Rajabi Michael Smith Nick Lewis is this something that can be worked on soon? It is currently blocking the installer team's ability to work on TOTES. Let us know either way so we can plan. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-592) Running Bolt task in CI to non-localhost fails
Title: Message Title Michael Smith commented on BOLT-592 Re: Running Bolt task in CI to non-localhost fails We added it to our board, so hopefully take a look at it this week. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-592) Running Bolt task in CI to non-localhost fails
Title: Message Title Nick Walker commented on BOLT-592 Re: Running Bolt task in CI to non-localhost fails Excellent, thanks for the update. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-592) Running Bolt task in CI to non-localhost fails
Title: Message Title Alex Dreyer commented on BOLT-592 Re: Running Bolt task in CI to non-localhost fails Do you have an ssh key configured for these nodes in ~/.ssh/config on your laptop but not in CI? What happens when you use ssh://localhost(localhost is special and will not use the ssh transport by default? This does not look like a bolt bug to me. I suggest sshing onto the node beaker is running on in CI and trying to connect from there. If that doesn't work pairing will probably be faster than treating this as a bug Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-503) Use local config automatically to embed bolt in a project
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-503 Use local config automatically to embed bolt in a project Change By: Kate Lopresti Labels: docs docs-reviewed feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8950) Fix external_ca_support tests in puppet server master
Title: Message Title Justin Stoller commented on PUP-8950 Re: Fix external_ca_support tests in puppet server master I re-ran the failing test with the latest code after PUP-8748 was in and it made points #1 and #2 moot, and I've re-written the fix for point #3. To fix it I've moved us from passing a string into the client for the url to passing the uri object with an updated path. This allows us to easily retrieve the host name (which is needed for error handling) from the client. I think it was valuable to have the client handle this error since its a pretty low level exception being raised and the client is abstracting connection management from the consumers. I looked into passing in our own Puppet::Rest::Route objects into the client or creating a value-ish object similar to Puppet::Network::HTTP::Site but it seemed like an invasive change when we are already passing a URI object to the blocks calling the client. Testing-wise I've used the error handling tests in Puppet::Network::HTTP::Connection as a template sharing the validator test objects and writing my own examples since we have to know a bit about the client or connection in each place. I've also added the fix discussed earlier for #2. It isn't manifesting itself currently but it seems like loading it, if able, as soon as possible, will make for more robust handling in the future. I also figured the comment in the code mentioning the weird monkey patching that httpclient is doing worth the commit on its own. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group
Jira (PUP-8950) Fix external_ca_support tests in puppet server master
Title: Message Title Justin Stoller updated an issue Puppet / PUP-8950 Fix external_ca_support tests in puppet server master Change By: Justin Stoller Fix Version/s: PUP 6.0.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-579) I want to know what output format bolt is using
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-579 I want to know what output format bolt is using Change By: Michael Smith Labels: docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-579) I want to know what output format bolt is using
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-579 I want to know what output format bolt is using Change By: Kate Lopresti Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-579) I want to know what output format bolt is using
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-579 I want to know what output format bolt is using Change By: Kate Lopresti Labels: docs docs-reviewed feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-592) Running Bolt task in CI to non-localhost fails
Title: Message Title Christopher Thorn commented on BOLT-592 Re: Running Bolt task in CI to non-localhost fails Alex Dreyer I've tried to simplify my testing scenario down to the basics, so I don't believe any of the node's SSH is configured, unless Beaker is handling that as part of the provision/setup process pre-pre-suite? I do agree with you that this isn't a Bolt bug, but more likely a bug in how I'm setting up my testing environment in our CI. But I'm at my wits end in coming up what I could possibly be doing wrong. Are there any examples in the modules that are using beaker-task-helper to install Bolt, that are not using localhost? I need to find time to get my testing environment setup with Jenkins, then I'll try the ssh://localhost and get back to you. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-592) Running Bolt task in CI to non-localhost fails
Title: Message Title Alex Dreyer commented on BOLT-592 Re: Running Bolt task in CI to non-localhost fails I meant ssh being configured on your laptop is probably the reason your tests work there but not in CI. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3768) puppet query environments generates json errors
Title: Message Title Adam Bottchen updated an issue PuppetDB / PDB-3768 puppet query environments generates json errors Change By: Adam Bottchen CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3768) puppet query environments generates json errors
Title: Message Title Eric Thompson updated an issue PuppetDB / PDB-3768 puppet query environments generates json errors Change By: Eric Thompson Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3768) puppet query environments generates json errors
Title: Message Title Eric Thompson updated an issue PuppetDB / PDB-3768 puppet query environments generates json errors Change By: Eric Thompson Method Found: Needs Assessment Customer Feedback Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3768) puppet query environments generates json errors
Title: Message Title Eric Thompson assigned an issue to Rob Browning PuppetDB / PDB-3768 puppet query environments generates json errors Change By: Eric Thompson Assignee: AJ Roetker Rob Browning Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6729) NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6729 NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators Change By: Geoff Nichols Sprint: Windows Hopper 2018-06-13 , Windows 2018-06- 13 27 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-610) Make transport API public and allow custom transport configuration
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-610 Make transport API public and allow custom transport configuration Issue Type: Story Assignee: Unassigned Created: 2018/06/19 4:42 PM Priority: Normal Reporter: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit
Jira (PUP-8949) Package pip provide won't work with ensure latest and custom index
Title: Message Title Anton Fomenko updated an issue Puppet / PUP-8949 Package pip provide won't work with ensure latest and custom index Change By: Anton Fomenko Affects Version/s: PUP 5.5.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-611) Minor Docs typo
Title: Message Title Glenn Sarti updated an issue Puppet Task Runner / BOLT-611 Minor Docs typo Change By: Glenn Sarti Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-611) Minor Docs typo
Title: Message Title Glenn Sarti updated an issue Puppet Task Runner / BOLT-611 Minor Docs typo Change By: Glenn Sarti Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-611) Minor Docs typo
Title: Message Title Glenn Sarti created an issue Puppet Task Runner / BOLT-611 Minor Docs typo Issue Type: Bug Assignee: Unassigned Created: 2018/06/19 10:50 PM Priority: Normal Reporter: Glenn Sarti In https://puppet.com/docs/bolt/0.x/bolt_configure_orchestrator.html#adjust-the-orchestrator-configuration-files it looks like the "f" was not set "escaped" properly in markdown. Image Attached. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-611) Minor Docs typo
Title: Message Title Glenn Sarti commented on BOLT-611 Re: Minor Docs typo 60039 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-611) Minor Docs typo
Title: Message Title Glenn Sarti updated an issue Puppet Task Runner / BOLT-611 Minor Docs typo Change By: Glenn Sarti In https://puppet.com/docs/bolt/0.x/bolt_configure_orchestrator.html#adjust-the-orchestrator-configuration-files it looks like the "f" was not set "escaped" properly in markdown. And the "for Windows" was "escaped" but shouldn't be. Image Attached. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-612) Some docs only list unix paths, not Windows
Title: Message Title Glenn Sarti created an issue Puppet Task Runner / BOLT-612 Some docs only list unix paths, not Windows Issue Type: Improvement Assignee: Unassigned Created: 2018/06/19 10:57 PM Priority: Normal Reporter: Glenn Sarti Some parts of the documentation only list Unix style paths, missing out it's equivalent in Windows. This is confusing for Windows users attempting to A) read the docs and B) use Bolt on Windows; https://puppet.com/docs/bolt/0.x/new_features.html#local-default-configuration-directory-boltdir-0-21-0 https://puppet.com/docs/bolt/0.x/new_features.html#analytics-data-collection-0-20-6 https://puppet.com/docs/bolt/0.x/new_features.html#bolt-config-file-for-common-options-0-10-0 https://puppet.com/docs/bolt/0.x/bolt_options.html#concept-9325 https://puppet.com/docs/bolt/0.x/inventory_file_generating.html#usage No Windows help here https://puppet.com/docs/bolt/0.x/bolt_connect_puppetdb.html $HOME is a unix-ism, in windows it's %HOME% or $ENV:HOME for cmd.exe or powershell respectively https://puppet.com/docs/bolt/0.x/configuring_bolt.html Possible infractions https://puppet.com/docs/bolt/0.x/new_features.html#kereberos-support-added-0-7-0 Does this example actually work on Windows? https://puppet.com/docs/bolt/0.x/bolt_configuration_options.html#sample-bolt-config-file Add Comment
