Jira (PUP-6562) Limit transaction.failed_dependencies? verbosity
Title: Message Title Kris Bosland updated an issue Puppet / PUP-6562 Limit transaction.failed_dependencies? verbosity Change By: Kris Bosland Release Notes Summary: Failed dependency resources will now only be reported once.Other resources that depend on the failed resource that has already been reported will not cause them to be reported again, but the user will still get the skip message for each skipped resource. Release Notes: Enhancement 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-6562) Limit transaction.failed_dependencies? verbosity
Title: Message Title Josh Cooper commented on PUP-6562 Re: Limit transaction.failed_dependencies? verbosity Kris Bosland could you add release notes? 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-6562) Limit transaction.failed_dependencies? verbosity
Title: Message Title Josh Cooper commented on PUP-6562 Re: Limit transaction.failed_dependencies? verbosity Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/b25698ffc0f3826fd2b7a33f2bb61ffa2d833be8 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-6562) Limit transaction.failed_dependencies? verbosity
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6562 Limit transaction.failed_dependencies? verbosity Change By: Josh Cooper Fix Version/s: PUP 5.5.z Fix Version/s: PUP 6.2.0 Fix Version/s: PUP 6.0.5 Fix Version/s: PUP 5.5.9 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (BOLT-1073) Notice level logger is not configured during plan tests
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1073 Notice level logger is not configured during plan tests Issue Type: Bug Assignee: Unassigned Created: 2019/01/04 4:22 PM Priority: Normal Reporter: Alex Dreyer The BoltSpec::Plan helper does not ensure that the notice level log method is added it should call initialize logging. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1010) Handle exceptions when parsing target URI
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1010 Handle exceptions when parsing target URI Change By: Cas Donoghue 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-1072) Add expect/allow_plan helpers to BoltSpec::plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1072 Add expect/allow_plan helpers to BoltSpec::plan Change By: Alex Dreyer 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-1072) Add expect/allow_plan helpers to BoltSpec::plan
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1072 Add expect/allow_plan helpers to BoltSpec::plan Issue Type: New Feature Assignee: Unassigned Created: 2019/01/04 3:03 PM Priority: Normal Reporter: Alex Dreyer https://github.com/puppetlabs/bolt/blob/master/lib/bolt_spec/plans.rb#L50 this was requested in slack Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4184) Add Kubernetes deployment descriptors
Title: Message Title Robert Roland updated an issue PuppetDB / PDB-4184 Add Kubernetes deployment descriptors Change By: Robert Roland Release Notes: Not Needed 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-9398) Race condition exists when cron resource specified but cron is not installed and gets installed by puppet
Title: Message Title
Joseph Marcelletti updated an issue
Puppet / PUP-9398
Race condition exists when cron resource specified but cron is not installed and gets installed by puppet
Change By:
Joseph Marcelletti
*Puppet Version: All tested (latest)* *Puppet Server Version: 4, 5, 6.1.0* *OS Name/Version: Centos 6/7*When a system does not have a cron handler installed, but the manifest installs cron and then installs a cron entry for a user, the cron entry will NOT get added to the user but instead to root. If you run again it will install for the user. This is obviously not intended and can potentially create a security risk (as cronjobs will run as root unintended). More importantly, it breaks stuff.Here is a sample that you can replace your site.pp with and run against an agent to reproduce:{code}# Make sure cronie is NOT installed (or any cron provider) for the sample race condition.package { 'cronie': ensure => installed,}cron { 'race_condition_test': ensure => present, user => 'nobody', # This can be any user as long as they exist. minute => '*/30', command => '/bin/false', require => Package['cronie'],}{code} The first time you run this it will install cronie, and install this crontab under root.Every time you run after it will install / verify the cron entry exists for the user 'nobody'.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9398) Race condition exists when cron resource specified but cron is not installed and gets installed by puppet
Title: Message Title
Joseph Marcelletti updated an issue
Puppet / PUP-9398
Race condition exists when cron resource specified but cron is not installed and gets installed by puppet
Change By:
Joseph Marcelletti
*Puppet Version: All tested (latest)* *Puppet Server Version: 4, 5, 6.1.0* *OS Name/Version: Centos 6/7*When a system does not have a cron handler installed, but the manifest installs cron and then installs a cron entry for a user, the cron entry will NOT get added to the user but instead to root. If you run again it will install for the user. This is obviously not intended and can potentially create a security risk (as cronjobs will run as root unintended). More importantly, it breaks stuff.Here is a sample that you can replace your site.pp with and run against an agent to reproduce: {code} # Make sure cronie is NOT installed (or any cron provider) for the sample race condition.package { 'cronie':ensure => installed,}cron { 'race_condition_test':ensure => present,user => 'nobody', # This can be any user as long as they exist.minute => '*/30',command => '/bin/false',require => Package['cronie'],} {code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9398) Race condition exists when cron resource specified but cron is not installed and gets installed by puppet
Title: Message Title
Joseph Marcelletti updated an issue
Puppet / PUP-9398
Race condition exists when cron resource specified but cron is not installed and gets installed by puppet
Change By:
Joseph Marcelletti
*Puppet Version: All tested (latest)* *Puppet Server Version: 4, 5, 6.1.0* *OS Name/Version: Centos 6/7*When a system does not have a cron handler installed, but the manifest installs cron and then installs a cron entry for a user, the cron entry will NOT get added to the user but instead to root. If you run again it will install for the user. This is obviously not intended and can potentially create a security risk (as cronjobs will run as root unintended). More importantly, it breaks stuff.Here is a sample that you can replace your site.pp with and run against an agent to reproduce:{code}# Make sure cronie is NOT installed (or any cron provider) for the sample race condition.package { 'cronie':ensure => installed,}cron { 'race_condition_test':ensure => present,user => 'nobody', # This can be any user as long as they exist.minute => '*/30',command => '/bin/false',require => Package['cronie'],}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9398) Race condition exists when cron resource specified but cron is not installed and gets installed by puppet
Title: Message Title
Joseph Marcelletti created an issue
Puppet / PUP-9398
Race condition exists when cron resource specified but cron is not installed and gets installed by puppet
Issue Type:
Bug
Affects Versions:
PUP 6.1.0, PUP 5.3.6
Assignee:
Unassigned
Created:
2019/01/04 1:52 PM
Priority:
Normal
Reporter:
Joseph Marcelletti
Puppet Version: All tested (latest) Puppet Server Version: 4, 5, 6.1.0 OS Name/Version: Centos 6/7 When a system does not have a cron handler installed, but the manifest installs cron and then installs a cron entry for a user, the cron entry will NOT get added to the user but instead to root. If you run again it will install for the user. This is obviously not intended and can potentially create a security risk (as cronjobs will run as root unintended). More importantly, it breaks stuff. Here is a sample that you can replace your site.pp with and run against an agent to reproduce:
Make sure cronie is NOT installed (or any cron provider) for the sample race condition. package { 'cronie': ensure => installed, }
cron { 'race_condition_test': ensure => present, user => 'nobody', # This can be any user as long as they exist. minute => '*/30', command => '/bin/false', require => Package['cronie'], }
Jira (PUP-9364) puppet module install is really slow
Title: Message Title Kris Bosland commented on PUP-9364 Re: puppet module install is really slow Merged into 5.5.x at [f41a4f0](https://github.com/puppetlabs/puppet/commit/f41a4f02f3c9144fd662a089682b18afb9b16ec7) 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-9392) Text Fragmentation: Incomplete phrases in string resources
Title: Message Title Erwin Hom commented on PUP-9392 Re: Text Fragmentation: Incomplete phrases in string resources https://github.com/puppetlabs/puppet/blob/master/lib/puppet/pops/model/model_label_provider.rb https://github.com/puppetlabs/puppet/blob/master/lib/puppet/pops/label_provider.rb https://github.com/puppetlabs/puppet/blob/master/lib/puppet/pops/issues.rb 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-9397) yum package provider fails when run as non root during noop
Title: Message Title
Craig Genner created an issue
Puppet / PUP-9397
yum package provider fails when run as non root during noop
Issue Type:
Bug
Affects Versions:
PUP 5.5.8, PUP 4.10.0
Assignee:
Unassigned
Components:
Types and Providers
Created:
2019/01/04 12:31 PM
Priority:
Normal
Reporter:
Craig Genner
Puppet Version: 5.5.8 Puppet Server Version: NA OS Name/Version: CentOS 6 & 7 When running a puppet apply in `noop` mode as a non root user, the catalog fails to apply and errors "The yum provider can only be used as root". This is due to `lib/puppet/provider/package/yum.rb` line 29 where the package prefix errors if the apply is not done as root. Desired Behavior: $ puppet apply --noop -e 'package { "moreutils": ensure => installed}' Notice: Compiled catalog for centos7.localdomain in environment production in 1.35 seconds Notice: /Stage[main]/Main/Package[moreutils]/ensure: current_value purged, should be present (noop) Notice: Class[Main]: Would have triggered 'refresh' from 1 events Notice: Stage[main]: Would have triggered 'refresh' from 1 events Notice: Applied catalog in 0.27 seconds Actual Behavior: $ puppet apply --noop -e 'package { "moreutils": ensure => installed}' Notice: Compiled catalog for centos7.localdomain in environment production in 1.27 seconds Error: Failed to apply catalog: The yum provider can only be used as root It appears that the raising of the error does not take into account running in `noop` mode, I've tried to find out how to fix this but I;m not familiar enough with the puppet code.
Jira (PUP-9364) puppet module install is really slow
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9364 puppet module install is really slow Change By: Josh Cooper Release Notes Summary: Puppet module install will now only download the release metadata it needs to perform dependency resolution, drastically reducing the amount of data transferred. For stdlib the reduction is from 25MB to 68KB, and any module that depends on stdlib will benefit when installed. 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 (PUP-9364) puppet module install is really slow
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9364 puppet module install is really slow Change By: Josh Cooper Fix Version/s: PUP 6.1.z Fix Version/s: PUP 6.2.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 (PUP-9364) puppet module install is really slow
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9364 puppet module install is really slow Change By: Josh Cooper 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 (PUP-8687) Should log JSON in newline-delimited format
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8687 Should log JSON in newline-delimited format Change By: Josh Cooper 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 (PUP-8687) Should log JSON in newline-delimited format
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8687
Should log JSON in newline-delimited format
Change By:
Josh Cooper
Release Notes Summary:
Puppet will log in newline - delimited JSON if the argument to the {{logdest}} setting or command line option is an absolute path and ends with the ".jsonl" extension , such as `puppet agent --logdest /var/log/puppet . jsonl`. This is preferrable preferable to the JSON format, since the generated log needed is not valid JSON and needs to have a closing ']' added appended to make it valid JSON .
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-8687) Should log JSON in newline-delimited format
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-8687
Should log JSON in newline-delimited format
Change By:
Josh Cooper
Release Notes Summary:
Puppet will log in newline delimited JSON if the argument to the {{logdest}} setting or command line option ends with the ".jsonl" extension. This is preferrable to the JSON format, since the log needed to have a closing ']' added to make it valid JSON.
Release Notes:
Enhancement
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-8687) Should log JSON in newline-delimited format
Title: Message Title Josh Cooper commented on PUP-8687 Re: Should log JSON in newline-delimited format Passed CI in e2d5394225dc4ba362febe6d29ad8f706fdbd77a 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-1065) Standard library functions were not packaged with Bolt
Title: Message Title Melissa Amos commented on BOLT-1065 Re: Standard library functions were not packaged with Bolt Docs update: http://docs-internal.puppet.com/docs/bolt/dev/bolt_resolved_issues.html#standard-library-functions-weren-t-packaged-in-1-8-0-1-8-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-1065) Standard library functions were not packaged with Bolt
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1065 Standard library functions were not packaged with Bolt Change By: Melissa Amos Labels: docs_reviewed 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-1071) Send release announcements (Bolt 1.8.1)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1071 Send release announcements (Bolt 1.8.1) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/01/04 9:47 AM Due Date: 2019/01/04 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-01-04) Once docs have finished building (check that all links resolve appropriately) - Create an e-mail announcement with the subject "Bolt 1.8.1 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.8.1 is now available".
Jira (BOLT-1066) Bolt 1.8.1 2019-01-04 Release
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1066 Bolt 1.8.1 2019-01-04 Release Issue Type: Task Assignee: Cas Donoghue Created: 2019/01/04 9:46 AM Priority: Normal Reporter: Cas Donoghue Bolt 1.8.1 2019-01-04 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1070) Docs for bolt release (Bolt 1.8.1)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1070 Docs for bolt release (Bolt 1.8.1) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/01/04 9:46 AM Due Date: 2019/01/04 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-01-04) Release notes and docs changes for bolt 1.8.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1069) Update homebrew-puppet (Bolt 1.8.1)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1069 Update homebrew-puppet (Bolt 1.8.1) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/01/04 9:46 AM Due Date: 2019/01/04 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-01-04) 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-1068) Kick off release pipeline (Bolt 1.8.1)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1068 Kick off release pipeline (Bolt 1.8.1) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/01/04 9:46 AM Due Date: 2019/01/04 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-01-04) 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-1067) Reconcile git commits, JIRA tickets, and versions (Bolt 1.8.1)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1067 Reconcile git commits, JIRA tickets, and versions (Bolt 1.8.1) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/01/04 9:46 AM Due Date: 2019/01/04 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-01-04) 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 (PUP-9372) Add collection operations to Puppet core
Title: Message Title Michael Smith updated an issue Puppet / PUP-9372 Add collection operations to Puppet core Change By: Michael Smith Team: Bolt 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-983) Add puma config for plan executor application
Title: Message Title David Kramer assigned an issue to Nick Lewis Puppet Task Runner / BOLT-983 Add puma config for plan executor application Change By: David Kramer Assignee: Lucy Wyman Nick Lewis 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-1010) Handle exceptions when parsing target URI
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-1010 Handle exceptions when parsing target URI Change By: Cas Donoghue Assignee: Cas Donoghue 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-1065) Standard library functions were not packaged with Bolt
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-1065 Standard library functions were not packaged with Bolt Change By: Michael Smith Release Notes Summary: Bolt 1.8.0 intended and failed to include new standard library functions. This release now includes them in the gem and packages. 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-1065) Standard library functions were not packaged with Bolt
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-1065 Standard library functions were not packaged with Bolt 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-1065) Standard library functions were not packaged with Bolt
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-1065 Standard library functions were not packaged with Bolt Issue Type: Bug Affects Versions: BOLT 1.8.0 Assignee: Unassigned Created: 2019/01/04 9:20 AM Fix Versions: BOLT Next Priority: Major Reporter: Michael Smith Bolt 1.8.0 intended to include new standard library functions, but they were not added to the gemspec and thus omitted from packages. Add Comment
Jira (PUP-1053) Resource defaults and automatic tags are applied after collectors are evaluated
Title: Message Title Henrik Lindberg commented on PUP-1053 Re: Resource defaults and automatic tags are applied after collectors are evaluated Martin Alfke I think that is a much better solution as it is not based on the order of tagging operations. Closing this ticket as a Won't Do. 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-1053) Resource defaults and automatic tags are applied after collectors are evaluated
Title: Message Title
Martin Alfke commented on PUP-1053
Re: Resource defaults and automatic tags are applied after collectors are evaluated
Henrik Lindbergthank you for explanation. I found a solution using filter function on data hashes. ``` $hash = { 'tom' => { uid => '1001', tag => ['admin'], } , 'ben' => { uid => '1100', tag => [ 'app1', 'app2', ] } } $admins = $hash.filter |$key, $value| { 'admin' in $value['tag'] } $app1 = $hash.filter | $key, $value| { 'app1' in $value['tag'] } $all_users = $admins.merge($app1) notify { "All users: ${all_users}": } ``` Fom my point of view we can close this ticket, as there now is a working solution available using Puppet lambda.
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.
