Jira (BOLT-971) Some functions not available in BoltSpec run_plan
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-971 Some functions not available in BoltSpec run_plan Change By: Melissa Amos Labels: docs_reviewed resolved-issue-added 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-9293) read_wide_string hides errors if the string is nil
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9293 read_wide_string hides errors if the string is nil Change By: Josh Cooper Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9312) puppet package provider fails when reading from registry
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9312 puppet package provider fails when reading from registry Change By: Josh Cooper Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-959) Plan with no return value is never marked complete in PE
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-959 Plan with no return value is never marked complete in PE Change By: Melissa Amos Labels: docs_reviewed resolved-issue-added 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-9311) User resource doesn't remove user from windows group
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9311 User resource doesn't remove user from windows group Change By: Josh Cooper Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9313) String#to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9313 String#to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows Change By: Josh Cooper Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9313) String#to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows
Title: Message Title Josh Cooper commented on PUP-9313 Re: String#to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows Posted to rubyinstaller.org 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-962) docker transport
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-962 docker transport Change By: Melissa Amos Labels: docs docs_reviewed puppercon 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-9313) String#to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9313 String#to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows Change By: Josh Cooper Summary: Psych String # dump to_yaml behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9313) Psych#dump behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows
Title: Message Title
Josh Cooper created an issue
Puppet / PUP-9313
Psych#dump behaves differently with ruby 2.4.5-1 and 2.5.3-1 on Windows
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/11/13 4:15 PM
Priority:
Normal
Reporter:
Josh Cooper
Ruby released bug+security fixes in ruby 2.4.5p335 and 2.5.3p105. For some reason, the Windows versions no longer emit the YAML document end tag (aka triple dots). Given yaml.rb containing:
require 'yaml'
puts "Ruby #{RUBY_VERSION}p#{RUBY_PATCHLEVEL}"
puts "Psych #{Psych::VERSION}"
puts "string".to_yaml
Jira (PDB-4184) Adding Kubernetes deployment descriptors
Title: Message Title Robert Roland updated an issue PuppetDB / PDB-4184 Adding Kubernetes deployment descriptors Change By: Robert Roland Labels: puppercon Team: PuppetDB Summary: (puppercon) Adding Kubernetes deployment descriptors Component/s: PuppetDB These are basic Write Kubernetes deployment descriptors . They do not have SSL support and use a hardcoded password. Helm chart for deploying PDB Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4184) (puppercon) Adding Kubernetes deployment descriptors
Title: Message Title Robert Roland assigned an issue to Robert Roland PuppetDB / PDB-4184 (puppercon) Adding Kubernetes deployment descriptors Change By: Robert Roland Assignee: Robert Roland 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-4184) (puppercon) Adding Kubernetes deployment descriptors
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4184 (puppercon) Adding Kubernetes deployment descriptors Issue Type: Bug Assignee: Unassigned Created: 2018/11/13 1:09 PM Priority: Normal Reporter: gepetto-bot These are basic Kubernetes deployment descriptors. They do not have SSL support and use a hardcoded password. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-971) Some functions not available in BoltSpec run_plan
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-971 Some functions not available in BoltSpec run_plan Change By: Michael Smith Release Notes: Bug Fix 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-973) Reconcile git commits, JIRA tickets, and versions (Bolt 1.3.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-973 Reconcile git commits, JIRA tickets, and versions (Bolt 1.3.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2018/11/13 10:04 AM Due Date: 2018/11/14 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2018-11-14) 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-976) Docs for bolt release (Bolt 1.3.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-976 Docs for bolt release (Bolt 1.3.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2018/11/13 10:04 AM Due Date: 2018/11/14 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2018-11-14) Release notes and docs changes for bolt 1.3.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-975) Update homebrew-puppet (Bolt 1.3.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-975 Update homebrew-puppet (Bolt 1.3.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2018/11/13 10:04 AM Due Date: 2018/11/14 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2018-11-14) 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 Run "rake 'brew:cask[puppet-bolt]'" Verify Casks/puppet-bolt.rb was updated to the correct version Put up a PR to homebrew-puppet and request review Add Comment
Jira (BOLT-974) Kick off release pipeline (Bolt 1.3.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-974 Kick off release pipeline (Bolt 1.3.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2018/11/13 10:04 AM Due Date: 2018/11/14 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2018-11-14) 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-977) Send release announcements (Bolt 1.3.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-977 Send release announcements (Bolt 1.3.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2018/11/13 10:04 AM Due Date: 2018/11/14 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2018-11-14) Once docs have finished building (check that all links resolve appropriately) - Create an e-mail announcement with the subject "Bolt 1.3.0 now available". Include a summary of the release and links to the installation instructions and release notes. In the From: field, enter the Google account Puppet Product Updates (puppet-product-upda...@puppet.com). In the Bcc: field, enter the following addresses. Send a separate message to each: internal-puppet-product-upda...@puppet.com, puppet-us...@googlegroups.com, puppet-...@googlegroups.com, and puppet-annou...@googlegroups.com. 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 1.3.0 is now available".
Jira (BOLT-972) Bolt 1.3.0 2018-11-14 Release
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-972 Bolt 1.3.0 2018-11-14 Release Issue Type: Task Assignee: Cas Donoghue Created: 2018/11/13 10:04 AM Priority: Normal Reporter: Cas Donoghue Bolt 1.3.0 2018-11-14 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-971) Some functions not available in BoltSpec run_plan
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-971 Some functions not available in BoltSpec run_plan Change By: Michael Smith 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-510) I want to name nodes in inventory separately from their URL/hostname
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-510
I want to name nodes in inventory separately from their URL/hostname
Change By:
Alex Dreyer
When using a lot of local vms or docker nodes it would be nice to be able to name node separately from their url to make it easier to refer to individual nodes and make log messages about those nodes more readable.Workarounds:- For referring to nodes you can create a named subgroup for each node.- For ssh nodes you can accomplish this naming in ssh config. questions Solution :- Is Add a new "uri" option to targets in inventory.- When specified the URI will be passed to the inventory object as the first argument and the name passed in options.- If no name was specified $target.name should return the uri otherwise it should return the name.- {{get_targets(name)}} should return the target by name- target should be able to be referenced \ from other groups by name{noformat}---groups: - name: group1nodes: - mytargetconfig: transport: ssh - name group2 nodes: - name: mytargeturi: localhost:2002{noformat}Problem:- It would be better if name defaulted to URI rather then having URI default to name. this useful would allow a target to be specified with host/port outside of getting started/testing? of the URI. We can consider making this change in 2.0 or with a new inventory file version but for now the relationship should go both ways. - How shuold If a target has both a name and a uri should {{ get_targets handle (uri)}} return the url when the node is also named target or a new target ? How should referencing from another group by uri?
Add Comment
Jira (BOLT-864) Always upload code from bolt when running a task via Orchestrator
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-864 Always upload code from bolt when running a task via Orchestrator Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-962) docker transport
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-962 docker transport Change By: Michael Smith 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-962) docker transport
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-962 docker transport Change By: Michael Smith 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-962) docker transport
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-962 docker transport Change By: Michael Smith Release Notes Summary: Add a Docker transport for executing directly on container instances with the Docker API. 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-4183) Consider adding env vars for some/all of puppetdb's config settings
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-4183 Consider adding env vars for some/all of puppetdb's config settings 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 (PDB-4183) Consider adding env vars for some/all of puppetdb's config settings
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4183 Consider adding env vars for some/all of puppetdb's config settings Issue Type: Task Assignee: Unassigned Created: 2018/11/13 8:37 AM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this
Jira (PDB-3924) Avoid temp file flood during fact path gc
Title: Message Title Charlie Sharpsteen commented on PDB-3924 Re: Avoid temp file flood during fact path gc We also observed this during an upgrade when migration 66 was being applied: https://github.com/puppetlabs/puppetdb/blob/6.0.1/src/puppetlabs/puppetdb/scf/migrate.clj#L1472-L1481 Postgresql work_mem had to be temporarily boosted to 2 GB in order to get through the migration — otherwise the 4 hour service startup timeout was tripped and the upgrade failed. If there is a general solution to this problem, then migration 66 should be re-written to avoid tempfile generation. 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-9257) Improve heredoc syntax checkers
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9257 Improve heredoc syntax checkers Change By: Henrik Lindberg Issue Type: Improvement 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 (PUP-9257) Improve heredoc syntax checkers
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9257 Improve heredoc syntax checkers Change By: Henrik Lindberg Release Notes Summary: Heredoc supported syntax checking (for example ` @(EOT:json) ) ` was earlier only performed during evaluation. Now it is instead performed when validating if this is possible ( that is when heredoc does not have any interpolated expressions). This means that `puppet parser validate` will now find and report issues in such heredocs.We also added support for `pp` and `epp` syntax checking to heredocs. Thus enabling `parser validate` to validate your inline EPP templates that are in heredocs. For example using `@(EOT:epp)` to validate the heredoc content as `epp`. 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-9308) stack level too deep (SystemStackError)
Title: Message Title Henrik Lindberg commented on PUP-9308 Re: stack level too deep (SystemStackError) Can you share that file so that we have something to test with? If it contains sensitive information, can you perhaps share it with me privately? 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.
