Jira (BOLT-158) Bolt should run .pp tasks with puppet on windows
Title: Message Title
John Duarte commented on BOLT-158
Re: Bolt should run .pp tasks with puppet on windows
Using bolt at SHA d4b5094, this passes manual validation.
Tested on Windows 10 Enterprise With puppet-agent version 5.3.2 installed.
PS C:\Users\Administrator> puppet --version
5.3.2
Create puppet task
PS C:\Users\Administrator> type .\modules\test\tasks\init.pp
file { 'c:/testfile.txt':
ensure => present,
content => 'Created by bolt task',
}
Bolt succeeds in running the task
Jira (PUP-8113) Remove incorrect deprecation warning for `audit` metaparam
Title: Message Title Garrett Guillotte commented on PUP-8113 Re: Remove incorrect deprecation warning for `audit` metaparam Removing the deprecation warning from lib/puppet/type.rb will remove it from the docs when we generate references for 4.10.8 and 5.3.2. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8100) Create mountpoint for locale files on master
Title: Message Title Maggie Dreyer commented on PUP-8100 Re: Create mountpoint for locale files on master Merged to 5.3.x at https://github.com/puppetlabs/puppet/commit/22d3908c61dc9cab61a16fc93c8e4d9642bb7ba0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8113) Remove incorrect deprecation warning for `audit` metaparam
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8113 Remove incorrect deprecation warning for `audit` metaparam Change By: Maggie Dreyer When we decided not to remove the audit metaparameter, we forgot to remove the corresponding deprecation warning stating the metaparam would be removed. We should get rid of the deprecation warning.For details on the audit metaparameter can be found here: https://puppet.com/docs/puppet/5.3/metaparameter.html#audit (and there also appears to be a stray deprecation warning in the docs for it that should also be removed). This should be merged first to the 4.10.x stream and then merged up. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8113) Remove incorrect deprecation warning for `audit` metaparam
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8113 Remove incorrect deprecation warning for `audit` metaparam Change By: Maggie Dreyer Acceptance Criteria: * Puppet no longer issues a deprecation warning for the audit metaparam *The docs no longer state that audit is deprecated Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8113) Remove incorrect deprecation warning for `audit` metaparam
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8113 Remove incorrect deprecation warning for `audit` metaparam Change By: Maggie Dreyer When we decided not to remove the audit metaparameter, we forgot to remove the corresponding deprecation warning stating it the metaparam would be removed. We should get rid of the deprecation warning. For details on the audit metaparameter can be found here: https://puppet.com/docs/puppet/5.3/metaparameter.html#audit (and there also appears to be a stray deprecation warning in the docs for it that should also be removed). Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8113) Remove incorrect deprecation warning for `audit` metaparam
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-8113 Remove incorrect deprecation warning for `audit` metaparam Issue Type: Bug Affects Versions: PUP 5.3.2, PUP 4.10.8 Assignee: Unassigned Created: 2017/11/01 3:38 PM Priority: Normal Reporter: Maggie Dreyer When we decided not to remove the audit metaparameter, we forgot to remove the corresponding deprecation warning stating it would be removed. We should get rid of the deprecation warning. Add Comment
Jira (PUP-8095) User {purge_ssh_keys => true, } not removing all keys
Title: Message Title
Jennifer Solman assigned an issue to Jennifer Solman
Puppet / PUP-8095
User {purge_ssh_keys => true, } not removing all keys
Change By:
Jennifer Solman
Assignee:
Jennifer Solman
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-893) Deprecate puppet inspect and the audit metaparameter
Title: Message Title Maggie Dreyer commented on PUP-893 Re: Deprecate puppet inspect and the audit metaparameter I'll file a new ticket to remove that deprecation warning and close this ticket again. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3738) Reports sync summary query is very slow
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3738 Reports sync summary query is very slow Change By: Jeff Yarnell Sprint: Data Platform 2017-11-01 , Data Platform 2017-11-15 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3723) Use JSONB for fact storage
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3723 Use JSONB for fact storage Change By: Jeff Yarnell Sprint: Data Platform 2017-11-01 , Data Platform 2017-11-15 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3560) Uncomment file-with-binary-template test once the relevant puppet pr is merged
Title: Message Title Jeff Yarnell updated an issue PuppetDB / PDB-3560 Uncomment file-with-binary-template test once the relevant puppet pr is merged Change By: Jeff Yarnell Sprint: Data Platform 2017-11-01 , Data Platform 2017-11-15 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1792) Backport platform fact acceptance test changes from 3.9.x -> 3.6.x
Title: Message Title Scott Garman created an issue Facter / FACT-1792 Backport platform fact acceptance test changes from 3.9.x -> 3.6.x Issue Type: Task Assignee: Unassigned Created: 2017/11/01 1:58 PM Priority: Normal Reporter: Scott Garman When adding new platforms, the facter merge-ups from 3.6.x -> 3.9.x are problematic because the layout of some of the acceptance tests have changed to consolidate platform-specific acceptance tests into more generalized fact tests. For example, the acceptance/tests/facts/el.rb file doesn't exist in 3.9.x and the tests it contains have been migrated into acceptance/tests/facts/os_processors_and_kernel.rb and identity.rb Let's just back-port these changes to 3.6.x so fumbling around with half-working merge-ups doesn't have to happen anymore. Add Comment
Jira (PUP-8097) Research: Evaluate VM Pooler processes in attempt to standardize
Title: Message Title Jennifer Solman commented on PUP-8097 Re: Research: Evaluate VM Pooler processes in attempt to standardize Progress: location for set up that all can contribute to: https://confluence.puppetlabs.com/pages/viewpage.action?pageId=159649086&moved=true Located and tested out documentation for VM floaty and bitbar. Made notes for workarounds. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8090) Load module translation files
Title: Message Title Michael Smith commented on PUP-8090 Re: Load module translation files We should try to load translations from both $modulepath and $vardir. I think initially, loading $vardir can skip the check to see if we've already loaded a translation file with that name. When we rework loading translations from modules, we'll want to remove that global caching anyway, which goes hand-in-hand with being more careful about when we try to load modules and when we invalidate the existing chain. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7883) Make node_terminus=ldap working with jruby/puppetserver
Title: Message Title Eric Delaney commented on PUP-7883 Re: Make node_terminus=ldap working with jruby/puppetserver Tested with SHA=b2e1f6a73bad625987bdac409900ebbd9ae355a3 SUITE_VERSION=5.3.2.118.gb2e1f6a Installed and configured an openldap server pointed puppet server as the ldap server node configuration: dn: cn=fmzl3pil20z4hvr,ou=production,ou=hosts,dc=ldaptest,dc=local objectclass: puppetClient objectclass: device puppetClass: base puppetClass: base2 puppetvar: role='bases' dn: cn=l16qsp2sdzt9cac,ou=production,ou=hosts,dc=ldaptest,dc=local objectclass: puppetClient objectclass: device
Jira (BOLT-205) Allow bolt script to run ruby and puppet manifests on Windows
Title: Message Title Josh Cooper created an issue Puppet Task Runner / BOLT-205 Allow bolt script to run ruby and puppet manifests on Windows Issue Type: New Feature Assignee: Unassigned Created: 2017/11/01 1:05 PM Priority: Normal Reporter: Josh Cooper Currently, bolt script run can only execute powershell scripts on Windows nodes, but bolt task/plan run can execute powershell, ruby and puppet manifests on Windows nodes. The difference is subtle and easily fixed using the process_from_extension helper in both places. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-158) Bolt should run .pp tasks with puppet on windows
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet Task Runner / BOLT-158 Bolt should run .pp tasks with puppet on windows Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-158) Bolt should run .pp tasks with puppet on windows
Title: Message Title John Duarte updated an issue Puppet Task Runner / BOLT-158 Bolt should run .pp tasks with puppet on windows Change By: John Duarte QA Risk Assessment: Needs Assessment Manual Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-158) Bolt should run .pp tasks with puppet on windows
Title: Message Title
John Duarte commented on BOLT-158
Re: Bolt should run .pp tasks with puppet on windows
Using bolt at SHA 3115817, this fails manual validation.
Tested on Windows 10 Enterprise With puppet-agent version 5.3.2 installed
PS C:\Users\Administrator> puppet --version
5.3.2
Create puppet task
PS C:\Users\Administrator> type .\modules\test\tasks\init.pp
file { 'c:/testfile.txt':
ensure => present,
content => 'Created by bolt task',
}
Puppet can successfully run .pp file
Jira (PUP-8090) Load module translation files
Title: Message Title Maggie Dreyer commented on PUP-8090 Re: Load module translation files So the way I'm reading the autoloader and fact loader code, it looks like for Ruby files, we load files from locally installed modules first, then pluginsynced stuff. Conversely for facts, we load pluginsynced stuff first, then local custom facts. In the case where there are no duplicate modules (and therefore no duplicate translations), this is fine. But it raises an interesting trade-off if there are both local and pluginsynced copies of data with the same name. The way we currently handle translation files, we only allow loading a PO file with a given name once. This means in the case where a user both has a module installed locally and has translations from a module of the same name pluginsynced, we will only load translations from whichever source we search first. Translations for all parts of a module (stuff in lib, facts, and manifests) are all loaded as one atomic PO file, one per module, so we can't choose different load orders from different parts. This could lead to surprising gaps in translations, that might be different across different operations. The alternative is to change the way we construct the text domains, to allow multiple repositories of the same name in a chain (note that the repository name HAS to correspond to the name of the PO file being loaded). We currently don't allow this because in the model where we were loading translations each time a module was loaded, this would have led to explosion of translations in memory, as well as tons of extra work. As we move to being more efficient about what we load and when, this might have less of an impact, but it could still lead to unnecessary duplicates, and it will remove any limit on the size of the repository chains (if we accidentally load things more times than we think we are, we will see the chains get very long). The benefit, however, is that we always will have all translations available in cases where we need to search both $modulepath and $vardir. Michael Smith or Josh Cooper thoughts? Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8111) Unsigned Redhat 5 guid rpm causes yum provider package test to fail
Title: Message Title Melissa Stone commented on PUP-8111 Re: Unsigned Redhat 5 guid rpm causes yum provider package test to fail https://github.com/puppetlabs/puppet/pull/6332 should fix this failure. I tested locally, and was able to reproduce the issue. Running the tests locally again with this change gave me a green run Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-98) Add sudo and sudo password prompt support
Title: Message Title Patrick Carlisle assigned an issue to Patrick Carlisle Puppet Task Runner / BOLT-98 Add sudo and sudo password prompt support Change By: Patrick Carlisle Assignee: Patrick Carlisle Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-168) Kerberos support for ssh
Title: Message Title John Duarte commented on BOLT-168 Re: Kerberos support for ssh Using bolt at SHA 3115817, this passes manual validation. Reproduction steps Test platform was Centos 7 x86_64 Setup kerberos Install packages yum install -y krb5-server krb5-libs krb5-workstation Create configuration file cat > /etc/krb5.conf << EOF includedir /etc/krb5.conf.d/ [logging] default = FILE:/var/log/krb5libs.log kdc = FILE:/var/log/krb5kdc.log admin_server = FILE:/var/log/kadmind.log
Jira (BOLT-98) Add sudo and sudo password prompt support
Title: Message Title Patrick Carlisle updated an issue Puppet Task Runner / BOLT-98 Add sudo and sudo password prompt support Change By: Patrick Carlisle Sprint: Tasks ELP (1.0) Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-204) Metadata should define dependency on the puppet agent.
Title: Message Title
Alex Dreyer created an issue
Puppet Task Runner / BOLT-204
Metadata should define dependency on the puppet agent.
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2017/11/01 11:37 AM
Priority:
Normal
Reporter:
Alex Dreyer
Many of the task we've written rely on the puppet agent package. Task authors should be able to indicate this in their metadata and task consumers should know whether a task requires the agent or not without looking at the task code.
The field for specifying this should be extendable to support additional dependencies in the future something like
{ "dependencies": { "puppet": { } }
or to match metadata.json
{ "dependencies": [ {"name": "puppet"} ] }
Jira (PUP-8111) Unsigned Redhat 5 guid rpm causes yum provider package test to fail
Title: Message Title Casey Williams commented on PUP-8111 Re: Unsigned Redhat 5 guid rpm causes yum provider package test to fail https://github.com/puppetlabs/puppet/commit/7cda3066aff208fc5cba4cf382358f0b1f7169c4 introduced this failure - it will be fixed as part of PUP-3323. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3323) yum provider should be able to install from remote URLs
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-3323 yum provider should be able to install from remote URLs Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4647) Yum provider uses rpm -e to uninstall packages
Title: Message Title Thomas Kishel commented on PUP-4647 Re: Yum provider uses rpm -e to uninstall packages Found ... https://projects.puppetlabs.com/issues/1739 yum package provider should erase packages The yum package provider currently runs ‘rpm -e PKG’ when it’s told to uninstall something (ensure => absent). To make it possible to uninstall packages with cyclic dependencies, it would be much better to have it run ‘yum -y erase PKG’. Doing that is a lot more dangerous, since it will uninstall PKG and everything that depends on it, but with that danger comes the power that some users need. https://github.com/puppetlabs/puppet/commit/d5e19f18eddd0d6ddb9818dabc873b3203335f95 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-182) scrum process improvement placeholder ticket
Title: Message Title Eric Thompson created an issue Puppet Strings / PDOC-182 scrum process improvement placeholder ticket Issue Type: Task Assignee: Eric Thompson Created: 2017/11/01 10:49 AM Priority: Normal Reporter: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8112) Archived file lists are missing for Jenkins unimatrix jobs
Title: Message Title Casey Williams updated an issue Puppet / PUP-8112 Archived file lists are missing for Jenkins unimatrix jobs Change By: Casey Williams Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8112) Archived file lists are missing for Jenkins unimatrix jobs
Title: Message Title Casey Williams created an issue Puppet / PUP-8112 Archived file lists are missing for Jenkins unimatrix jobs Issue Type: Task Assignee: Sean McDonald Created: 2017/11/01 10:39 AM Priority: Normal Reporter: Casey Williams Jenkins used to list archived files for agent builds at the top of job pages; This went away after the advent of the unimatrix, but it should be re-enabled, since it's helpful for debugging transients. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8111) Unsigned Redhat 5 guid rpm causes yum provider package test to fail
Title: Message Title Casey Williams created an issue Puppet / PUP-8111 Unsigned Redhat 5 guid rpm causes yum provider package test to fail Issue Type: CI Blocker Assignee: Unassigned Created: 2017/11/01 10:30 AM Fix Versions: PUP 5.3.4 Priority: Normal Reporter: Casey Williams The failed job: https://jenkins-master-prod-1.delivery.puppetlabs.net/job/platform_puppet-agent_puppet-agent-integration-suite_daily-master/COMPONENT=puppet,SLAVE_LABEL=beaker,TEST_TARGET=redhat5-64a/10/ Relevant error text: Total size: 29 Downloading Packages:
Jira (PUP-3323) yum provider should be able to install from remote URLs
Title: Message Title Maggie Dreyer commented on PUP-3323 Re: yum provider should be able to install from remote URLs This failed in CI, looks like the added acceptance test may not be quite right: https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent/view/master/view/Suite/job/platform_puppet-agent_puppet-agent-integration-suite_daily-master/10/COMPONENT=puppet,SLAVE_LABEL=beaker,TEST_TARGET=redhat5-64a/testReport/(root)/tests_resource_package/yum_rb/ Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6739) Error running puppet with non-existent and non-default environment
Title: Message Title Melissa Stone updated an issue Puppet / PUP-6739 Error running puppet with non-existent and non-default environment Change By: Melissa Stone Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6739) Error running puppet with non-existent and non-default environment
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-6739 Error running puppet with non-existent and non-default environment Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1784) hypervisors fact reports false positive for LPAR/WPAR on KVM power8
Title: Message Title Geoff Nichols assigned an issue to Enis Inan Facter / FACT-1784 hypervisors fact reports false positive for LPAR/WPAR on KVM power8 Change By: Geoff Nichols Assignee: Casey Williams Enis Inan Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1653) External Facts from PowerShell do not parse structured output (JSON/YAML)
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1653 External Facts from PowerShell do not parse structured output (JSON/YAML) Change By: Geoff Nichols Sprint: Platform OS Hold, Platform OS 2017-10-31 , Platform OS Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3742) Sync should skip records that are already present in the command queue
Title: Message Title Charlie Sharpsteen created an issue PuppetDB / PDB-3742 Sync should skip records that are already present in the command queue Issue Type: Improvement Affects Versions: PDB 5.1.3 Assignee: Unassigned Created: 2017/11/01 10:07 AM Priority: Normal Reporter: Charlie Sharpsteen PuppetDB sync compares the contents of two databases and transfers over any data that isn't present in the local database. If a large amount of data is transferred, a large command queue will be created which has to be worked off. This can result in several sync cycles transferring the same data before the first copy reaches the front of the command queue and is inserted into the database. PuppetDB sync should list the IDs of records in the queue at the beginning of sync and skip transferring any remote records that are included in the list. Add Comment
Jira (PDB-3741) Prioritize catalogs and facts during PDB sync
Title: Message Title Charlie Sharpsteen created an issue PuppetDB / PDB-3741 Prioritize catalogs and facts during PDB sync Issue Type: Improvement Affects Versions: PDB 5.1.3 Assignee: Unassigned Created: 2017/11/01 10:01 AM Priority: Normal Reporter: Charlie Sharpsteen Currently, PuppetDB syncs entities in the following order: reports facts catalogs nodes We should consider prioritizing catalogs and facts as catalogs are used in exported resource queries and facts are used for general queries such as targeting nodes for tasks. Additionally, if two PuppetDB nodes become partitioned, there is likely to be a significant amount of report data that needs to be transferred, which means a significant delay in repairing catalogs and facts so that queries are corrected. An updated ordering would be:
Jira (PUP-6355) Review page: Troubleshooting Puppet for Windows
Title: Message Title Craig Gomes assigned an issue to Claire Cadman Puppet / PUP-6355 Review page: Troubleshooting Puppet for Windows Change By: Craig Gomes Assignee: Glenn Sarti Claire Cadman Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-44) Display human-readable results from running a task
Title: Message Title Henrik Lindberg commented on BOLT-44 Re: Display human-readable results from running a task Alex Dreyer I am thinking when running plans. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-179) Could not parse PKey: no start line (ArgumentError)
Title: Message Title Josh Cooper updated an issue Puppet Task Runner / BOLT-179 Could not parse PKey: no start line (ArgumentError) Change By: Josh Cooper Sprint: Tasks ELP (1.0) Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-179) Could not parse PKey: no start line (ArgumentError)
Title: Message Title Josh Cooper commented on BOLT-179 Re: Could not parse PKey: no start line (ArgumentError) ah, I can repro now if I kill my ssh-agent process and try to use a non-VM pooler based host: $ bx bolt command run whoami -n XXX -k --debug 2017-11-01T08:46:14.701652 DEBUG executor: Started with 1 thread(s) 2017-11-01T08:46:14.702189 DEBUG executor: Authentication method 'gssapi-with-mic' is not available XXX Failed to connect to XXX: Could not parse PKey: no start line Add Comment
Jira (BOLT-151) Display results as they occur, instead of when all nodes finish
Title: Message Title Josh Cooper updated an issue Puppet Task Runner / BOLT-151 Display results as they occur, instead of when all nodes finish Change By: Josh Cooper Fix Version/s: BOLT 0.8.0 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-151) Display results as they occur, instead of when all nodes finish
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet Task Runner / BOLT-151 Display results as they occur, instead of when all nodes finish Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-151) Display results as they occur, instead of when all nodes finish
Title: Message Title Josh Cooper updated an issue Puppet Task Runner / BOLT-151 Display results as they occur, instead of when all nodes finish Change By: Josh Cooper Sprint: Tasks ELP (1.0) Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-44) Display human-readable results from running a task
Title: Message Title Alex Dreyer commented on BOLT-44 Re: Display human-readable results from running a task The output of running a single task on many nodes isn't very async because we don't know how to display each node until it's done. The output should completely print one node result before starting to print the next. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-30) Autoload plans
Title: Message Title Kenn Hussey updated an issue Puppet Task Runner / BOLT-30 Autoload plans Change By: Kenn Hussey Sprint: Tasks ELP (1.0) Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-31) Implement the run_plan() function
Title: Message Title Kenn Hussey updated an issue Puppet Task Runner / BOLT-31 Implement the run_plan() function Change By: Kenn Hussey Sprint: Tasks ELP (1.0) Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-20) rspec integration tests to execute against external SSH servers
Title: Message Title Kenn Hussey updated an issue Puppet Task Runner / BOLT-20 rspec integration tests to execute against external SSH servers Change By: Kenn Hussey Sprint: Tasks ELP (1.0) Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-49) Add a Command data type
Title: Message Title Kenn Hussey updated an issue Puppet Task Runner / BOLT-49 Add a Command data type Change By: Kenn Hussey Sprint: Tasks ELP (1.0) Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-97) Support node lists given on Bolt commandline as parameters of type Nodes
Title: Message Title Kenn Hussey updated an issue Puppet Task Runner / BOLT-97 Support node lists given on Bolt commandline as parameters of type Nodes Change By: Kenn Hussey Sprint: Tasks ELP (1.0) Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8096) Filtering resources by tag interferes with corrective vs. intentional change determination
Title: Message Title Pieter Loubser updated an issue Puppet / PUP-8096 Filtering resources by tag interferes with corrective vs. intentional change determination Change By: Pieter Loubser Sprint: SCR 2017-11-01 , SCR 2017-11-15 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-64) Create puppet-bolt repo and scaffolding
Title: Message Title Kenn Hussey updated an issue Puppet Task Runner / BOLT-64 Create puppet-bolt repo and scaffolding Change By: Kenn Hussey Sprint: Tasks ELP (1.0) Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-143) Support executing whitelisted executables based on file extension in Windows
Title: Message Title Kenn Hussey updated an issue Puppet Task Runner / BOLT-143 Support executing whitelisted executables based on file extension in Windows Change By: Kenn Hussey Sprint: Tasks ELP (1.0) Kanban Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7961) Create puppet-bolt gem
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7961 Create puppet-bolt gem Change By: Kenn Hussey Sprint: Tasks ELP (1.0) Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-106) run_task should return task results
Title: Message Title Kenn Hussey updated an issue Puppet Task Runner / BOLT-106 run_task should return task results Change By: Kenn Hussey Sprint: Tasks ELP (1.0) Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8096) Filtering resources by tag interferes with corrective vs. intentional change determination
Title: Message Title Steve Quin updated an issue Puppet / PUP-8096 Filtering resources by tag interferes with corrective vs. intentional change determination Change By: Steve Quin Sprint: SI Backlog - DAVIS, SCR 2017-11-01 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8096) Filtering resources by tag interferes with corrective vs. intentional change determination
Title: Message Title Pieter Loubser updated an issue Puppet / PUP-8096 Filtering resources by tag interferes with corrective vs. intentional change determination Change By: Pieter Loubser Sprint: SI Backlog - DAVIS, SCR 2017-11-01 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8096) Filtering resources by tag interferes with corrective vs. intentional change determination
Title: Message Title Pieter Loubser assigned an issue to Pieter Loubser Puppet / PUP-8096 Filtering resources by tag interferes with corrective vs. intentional change determination Change By: Pieter Loubser Assignee: Scott Walker Pieter Loubser Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1781) Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64
Title: Message Title Casey Williams commented on FACT-1781 Re: Facter acceptance tests fail printing a boost::optional on Solaris 10 x86_64 This recurred again on solaris10-sparc, solaris11-64, aix61-power,and aix71-power last night, which makes very little sense to me - the facter commit that fixed this in the 5.3.x branch is an ancestor of the one that went through master on this run: https://jenkins-master-prod-1.delivery.puppetlabs.net/job/platform_puppet-agent_intn-van-sys_suite-secondary-puppet-master/34/ I'll look at it again today and figure out what still needs to happen. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8094) Lookup ignores environment from the classifier when using rule with trusted facts
Title: Message Title Henrik Lindberg commented on PUP-8094 Re: Lookup ignores environment from the classifier when using rule with trusted facts Laura Macchi I think the choice is if by default the lookup CLI should show values using the node's current state (what lookup does now) or its future state (ENC gives it a different env than what is stored). I also suggested a route where user would be told that the ENC says it should have a different env, and that in order to see those values, the user will need to override the env on the command line. (Naturally, the opposite is also possible if we want the "future env" to be the default). What to do here is a UX/Product decision - technically it can be made to work either way. Ping Eric Sorenson. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8101) Optional[] data type doesn't allow a parameter to be disabled
Title: Message Title
Henrik Lindberg commented on PUP-8101
Re: Optional[] data type doesn't allow a parameter to be disabled
guess that I don't really see what the point of Optional is if it's so difficult to make an optional parameter. I don't think that a user should have to jump through hoops to do what seems like a straightforward task.
I regret that we named the data type Optional[T}, we should instead have used Undef[T] type since the meaning is "allows an undef value or instance of T" - essentially the same as the longer form Variant[Undef, T]. The name "optional" suggest that there is some kind of "optionality" involved in a particular context, but that is not the case. We did make this worse by allowing Optional around a key in a Struct to make the key optional (so, there we did use it for "optionality"). When used in a struct it you may have something like Optional[key] => Optional[String] which means "key may be missing, if it exists it can be set to undef or a String value". This complexity is needed since you want to be able to restrict a key such that "key may be missing, if set it must be a String value". If we apply the same kind of syntax to a parameter list, we end up with the hideous Optional[String] Optional[$bar] = 'something' (which may be unparseable). In order to truly support optionality for class and resource parameter we need a different marker - akin to the "splat" (for one or more values).
Thus, your original case could then be supported like this:
class myclass(Array ?$foo = ['a', 'b', 'c']) { ... }
The ? would mean "optional" and implies that the given type T is turned into Optional[T] unless undef is already assignable to T (that way you can skip wrapping the T). This syntax would provide the required information that you indeed want to be able to assign an undef value by using the resource expressions - that is, this would work:
class { 'myclass': foo => undef }
Unfortunately we cannot take a type of a parameter to which you can assign undef to mean that the parameter has "optionality" as that would be backwards incompatible and cause subtle breakage. I really wish I could go back in time and fix this...
Jira (PUP-8101) Optional[] data type doesn't allow a parameter to be disabled
Title: Message Title Henrik Lindberg commented on PUP-8101 Re: Optional[] data type doesn't allow a parameter to be disabled William Yardley When you have specified something like Optional[String] $x = 'something' as the type/default for a class parameter you can still get that to be undef by binding undef to in hiera and letting APL provide the value. You can however not give it in a manifest (because of the semantic rules of the puppet language). Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8101) Optional[] data type doesn't allow a parameter to be disabled
Title: Message Title Henrik Lindberg commented on PUP-8101 Re: Optional[] data type doesn't allow a parameter to be disabled Ben Ford True, there is no straight forward way to state that - IMO a flaw in the original design of the "undef means default" rule - that rule was implemented because there is no syntactical way to "not set attribute if given value is undef". You would get your suggested "array + false" if we add a type parameter to the Boolean type - I am in favor of that, I have wanted that for other purposes. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-44) Display human-readable results from running a task
Title: Message Title Henrik Lindberg commented on BOLT-44 Re: Display human-readable results from running a task Is there value in keeping the last result and re-display with a different format? We opted to do that for catalog preview because you may not want to run again (or cannot) but need to see details for a node. If output is async and mixed it becomes very hard to do something rational with it after the fact (scroll back is chaos). If done that way it would be possible to add cool features like jumping between watching the "tail" of different nodes as they are running, watching different nodes in different windows etc. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8067) Selector expression ignored in some scenarios
Title: Message Title Henrik Lindberg commented on PUP-8067 Re: Selector _expression_ ignored in some scenarios Eric Sorenson The affected body of code would be only new code as the 3.x parser had many restrictions - don't think you could even get to see this in 3.x with old parser. Still a risk, but smaller body of code. Trevor Robinson Totally agree that the behavior is bad; inconsistent with other languages, unintuitive, and it is unintentional. However, a change silently changes behaviour; existing code could "mysteriously" produce a different result. That kind of change is expensive as users have to review their code and "migrate" rather than "upgrade". It is close to impossible to warn about this and we would have to instrument the runtime logic to aid catalog preview to be able to diff the outcome. Given all that, and the fact that this is reported this late in the life of "future parser" (it has been this way since 3.8) is an indication that this cannot be a problem big enough to justify the cost of changing the precedence since there are work arounds: Use parentheses Use a case or if _expression_ With that, we will repurpose this ticket to better document the selector _expression_. Ping Jean Bond. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/pupp
