Jira (PDB-3751) PDB Sync should allow a separate setting for the maximum amount of reports to sync
Title: Message Title Owen Rodabaugh updated an issue PuppetDB / PDB-3751 PDB Sync should allow a separate setting for the maximum amount of reports to sync Change By: Owen Rodabaugh CS Priority: Needs Priority Normal CS Impact: Customers with a large number of reports, or who store more than the default days of reports will take a long time to sync those reports if they lose connectivity between PDB nodes. This would get their sync running again much faster.This is analogous to situations where customers run out of disk space on the postgres node. They can truncate the reports table to get running again if they don't need old reports. CS Severity: 3 - Serious CS Business Value: 4 - $ CS Frequency: 2 - 5-25% of Customers Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8141) Replace hardcoded use of md5 for FIPS compliance
Title: Message Title Jayant Sane updated an issue Puppet / PUP-8141 Replace hardcoded use of md5 for FIPS compliance Change By: Jayant Sane Acceptance Criteria: All puppet flows, except any module flows, should work in a mixed environment:Current puppet agents (not running in FIPS) w/ and without FIPS agents. Specifically: - Master's global digest_algorithm can be default md5- FIPS versions of agents should be provisioned using file resource with different source attributes of http, puppet and from within a module. - If possible case of upgrading existing agent to FIPS version Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1796) OSX puppet facts run in japanese with facter errors returns "invalid byte sequence in US-ASCII"
Title: Message Title Eric Delaney commented on FACT-1796 Re: OSX puppet facts run in japanese with facter errors returns "invalid byte sequence in US-ASCII" trace output xh734nh8owpuouo:~ root# LANGUAGE=ja_JP.UTF-8 puppet facts --trace Error: Facter: error while resolving custom fact "i18ndemo_fact": invalid byte sequence in US-ASCII backtrace: poparser.ry:162:in `===' poparser.ry:162:in `parse' /opt/puppetlabs/puppet/lib/ruby/gems/2.4.0/gems/fast_gettext-1.1.0/lib/fast_gettext/po_file.rb:35:in `parse_po_file' /opt/puppetlabs/puppet/lib/ruby/gems/2.4.0/gems/fast_gettext-1.1.0/lib/fast_gettext/po_file.rb:21:in `load_data' /opt/puppetlabs/puppet/lib/ruby/gems/2.4.0/gems/fast_gettext-1.1.0/lib/fast_gettext/mo_file.rb:40:in `data' /opt/puppetlabs/puppet/lib/ruby/gems/2.4.0/gems/fast_gettext-1.1.0/lib/fast_gettext/mo_file.rb:15:in `[]'
Jira (FACT-1796) OSX puppet facts run in japanese with facter errors returns "invalid byte sequence in US-ASCII"
Title: Message Title Eric Delaney commented on FACT-1796 Re: OSX puppet facts run in japanese with facter errors returns "invalid byte sequence in US-ASCII" xh734nh8owpuouo:~ root# for LOCALE in `locale -a | grep ja` > do > echo $LOCALE > LANGUAGE=$LOCALE puppet facts >/dev/null > done ja_JP Error: Facter: error while resolving custom fact "i18ndemo_fact": invalid byte sequence in US-ASCII ja_JP.eucJP Error: Facter: error while resolving custom fact "i18ndemo_fact": invalid byte sequence in US-ASCII ja_JP.SJIS
Jira (FACT-1796) OSX puppet facts run in japanese with facter errors returns "invalid byte sequence in US-ASCII"
Title: Message Title Eric Delaney updated an issue Facter / FACT-1796 OSX puppet facts run in japanese with facter errors returns "invalid byte sequence in US-ASCII" Change By: Eric Delaney Summary: OSX puppet facts run in japanese with facter errors returns "invalid byte sequence in US-ASCII" Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1796) OSX puppet facts run in japanese with facter errors returns "invalid byte sequence in US-ASCII"
Title: Message Title Eric Delaney updated an issue Facter / FACT-1796 OSX puppet facts run in japanese with facter errors returns "invalid byte sequence in US-ASCII" Change By: Eric Delaney Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1796) puppet facts run in japanese with facter errors returns "invalid byte sequence in US-ASCII"
Title: Message Title Eric Delaney created an issue Facter / FACT-1796 puppet facts run in japanese with facter errors returns "invalid byte sequence in US-ASCII" Issue Type: Bug Assignee: Unassigned Created: 2017/11/09 3:17 PM Priority: Normal Reporter: Eric Delaney If you load the eputnam-i18ndemo module which has a fact that causes and error that has a Japanese translation, when its run on OSX the error is replaced by "invalid byte sequence in US-ASCII" xh734nh8owpuouo:~ root# puppet module install eputnam-i18ndemo Notice: Preparing to install into /etc/puppetlabs/code/environments/production/modules ... Notice: Downloading from https://forgeapi.puppet.com ... Notice: Installing -- do not interrupt ...
Jira (PDB-3654) Bump puppetlabs-inifile dep upper range to 3.0.0
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3654 Bump puppetlabs-inifile dep upper range to 3.0.0 Change By: Zachary Kent Release Notes: Known Issue 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-3757) Convert select_facts to work with jsonb
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3757 Convert select_facts to work with jsonb Change By: Rob Browning Sprint: Hopper/Triage 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-3757) Convert select_facts to work with jsonb
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3757 Convert select_facts to work with jsonb Change By: Rob Browning Sprint: Hopper/Triage 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-3757) Convert select_facts to work with jsonb
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3757 Convert select_facts to work with jsonb Issue Type: Improvement Assignee: Unassigned Created: 2017/11/09 2:00 PM Priority: Normal Reporter: Rob Browning See puppetlabs.puppetdb.command-test/query-facts for relevant bits. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PDB-3654) Bump puppetlabs-inifile dep upper range to 3.0.0
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3654 Bump puppetlabs-inifile dep upper range to 3.0.0 Change By: Zachary Kent Release Notes Summary: Bumped the puppetlabs/inifile dependency upper range so that it matches the new version. 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-3756) Add fact_paths gc for jsonb overhaul
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3756 Add fact_paths gc for jsonb overhaul Issue Type: Improvement Assignee: Unassigned Created: 2017/11/09 1:55 PM Priority: Normal Reporter: Rob Browning 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
Jira (PDB-3756) Add fact_paths gc for jsonb overhaul
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3756 Add fact_paths gc for jsonb overhaul Change By: Rob Browning Assignee: Rob Browning 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-3654) Bump puppetlabs-inifile dep upper range to 3.0.0
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-3654 Bump puppetlabs-inifile dep upper range to 3.0.0 Change By: Zachary Kent Fix Version/s: PDB module-6.0.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 (PDB-3738) Reports sync summary query is very slow
Title: Message Title Jeff Yarnell commented on PDB-3738 Re: Reports sync summary query is very slow Just noticed there's a "needs fix version" swim lane too. You probably already have a step in the process for identifying fixVersions, but I'd like to understand what it is. 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-8140) NoMethodErrors involving Puppet::Face instances do not have a useful error message
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-8140 NoMethodErrors involving Puppet::Face instances do not have a useful error message Change By: Charlie Sharpsteen Labels: cs_pr_review 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-8140) NoMethodErrors involving Puppet::Face instances do not have a useful error message
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-8140 NoMethodErrors involving Puppet::Face instances do not have a useful error message Change By: Charlie Sharpsteen Summary: NoMethodErrors involving Puppet::Face instances do not have a useful text representation error message 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 commented on PDB-3738 Re: Reports sync summary query is very slow Russell Mull How do we determine which Platform/PE releases should be targeted for this fix? No fixVersion value(s) yet. /cc Nirupama Mantha 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-8142) Merge Strategy 'first|unique|hash' documentation is unclear
Title: Message Title Brian Vanderbusch commented on PUP-8142 Re: Merge Strategy 'first|unique|hash' documentation is unclear So an example use case that I want to determine if this merge strategy will work: My default merge strategies for most modules in my repo is `first`, however, I want to use either `unique` or `hash` (depending on the parameter type) for all of the parameters for an individual module that contains layer 3 data sources. The module has dozens of parameters, and I'd prefer my `lookup_strategy` config in `common.yaml` be simple: ``` lookup_strategy: '^some_profile:.*)': strategy: 'unique|hash' ``` As opposed to listing out the dozens of keys just to specify the same merge behavior for each hash or array parameter in the module. The documentation for `first|unique|hash` leaves me to guess that it tries to combine `unique` and `hash` by evaluating the type of data provided... but makes no sense that `first` would be there as well in this scenario. 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-8142) Merge Strategy 'first|unique|hash' documentation is unclear
Title: Message Title Brian Vanderbusch created an issue Puppet / PUP-8142 Merge Strategy 'first|unique|hash' documentation is unclear Issue Type: Improvement Assignee: Unassigned Components: DOCS Created: 2017/11/09 12:18 PM Priority: Normal Reporter: Brian Vanderbusch The documentation for the [`first|unique|hash`](https://puppet.com/docs/puppet/5.3/hiera_merging.html#strategy--firstuniquehash) merge strategy is brief, and does not explain usage or functionality of the merge strategy in a similar way to the documentation for the other merge strategies. The entirety of the current documentation for this strategy is one sentance: > Same as the string versions of these merge behaviors. This doesn't tell me anything, since obviously it's not the same, or it wouldn't be an additonal option. Mainly, I believe it's implying that hiera will try to select the appropriate strategy based on the data-type. However that raises the question of how the `unique` or `hash` strategy would be applied to a key when `first` is also present (which ignores all merge's entirely).
Jira (PUP-8141) Replace hardcoded use of md5 for FIPS compliance
Title: Message Title Jayant Sane created an issue Puppet / PUP-8141 Replace hardcoded use of md5 for FIPS compliance Issue Type: Task Assignee: Jayant Sane Created: 2017/11/09 11:47 AM Priority: Normal Reporter: Jayant Sane There are a couple of instances where MD5 is being hard coded in puppet. FIPS compliant versions of agents need to use one of the FIPS approved algorithms instead. Following places need to be changed: 1. Agents processing file resources specifying http as their source need to be able to accept checksums computed using hash alg other than md5. 2. fqdn_rand 3. Files synched to agents via the plugin-sync mechanism are checksummed using md5. That needs to be overridden to use a FIPS approved alg. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-8140) NoMethodErrors involving Puppet::Face instances do not have a useful text representation
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-8140 NoMethodErrors involving Puppet::Face instances do not have a useful text representation Change By: Charlie Sharpsteen Release Notes Summary: Error messages from Puppet::Face objects now include the name and version number of the face. Method Found: Needs Assessment Customer Feedback Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8095) User {purge_ssh_keys => true, } not removing all keys
Title: Message Title
Maggie Dreyer updated an issue
Puppet / PUP-8095
User {purge_ssh_keys => true, } not removing all keys
Change By:
Maggie Dreyer
Sprint:
Platform Core KANBAN
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8140) NoMethodErrors involving Puppet::Face instances do not have a useful text representation
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-8140
NoMethodErrors involving Puppet::Face instances do not have a useful text representation
Change By:
Charlie Sharpsteen
Acceptance Criteria:
The Puppet::Face class does not define a useful text representation for use in some error messages --- I.E. {{NoMethodError}}. This makes errors involving missing methods on Puppet Faces especially difficult to track down. Puppet Faces allow multiple versions, so these errors are easy to create by third-party modules defining a new Face version that other Puppet components don't expect.h2. Reproduction Case. - Install the latest puppet-agent 4.10.x on CentOS 7:{code:bash}rpm -Uvh http://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpmyum install -y puppet-agent{code} - Create a module containing a Puppet Face that can fail due to multiple versions:{code:bash}mkdir -p /etc/puppetlabs/code/environments/production/modules/test_face/lib/puppet/applicationcat < /etc/puppetlabs/code/environments/production/modules/test_face/lib/puppet/application/foo.rbrequire 'puppet/application/face_base'class Puppet::Application::Foo < Puppet::Application::FaceBaseendEOFmkdir -p /etc/puppetlabs/code/environments/production/modules/test_face/lib/puppet/facecat < /etc/puppetlabs/code/environments/production/modules/test_face/lib/puppet/face/foo.rbPuppet::Face.define(:foo, '0.0.1') do action :bar dowhen_invoked do |*args| puts "Bar action called!"end end action :baz dowhen_invoked do |*args| puts "Baz action called!" Puppet::Face[:foo, :current].barend endendPuppet::Face.define(:foo, '0.0.2') do action :bim dowhen_invoked do |*args| puts "Bim action called!"end endendEOF{code} - Run the face to generate a failure: {{/opt/puppetlabs/puppet/bin/puppet foo baz}}h3. OutcomeThe error message indicates no {{baz}} method is avaiailble, but provides no clue that Face versions are coming into play:{noformat}# /opt/puppetlabs/puppet/bin/puppet foo bazBaz action called!Error: undefined method `bar' for #Error: Try 'puppet help foo baz' for usage{noformat}h3. Expected OutcomeThe error message should include the face name and version number, as provided by the {{to_s}} method of the Puppet::Interface class:{noformat}# /opt/puppetlabs/puppet/bin/puppet foo bazBaz action called!Error: undefined method `bar' for Puppet::Face[:foo, v0.0.2]:Puppet::InterfaceError: Try 'puppet help foo baz' for usage{noformat}
Add Comment
Jira (FACT-1653) External Facts from PowerShell do not parse structured output (JSON/YAML)
Title: Message Title Geoff Nichols assigned an issue to Branan Riley Facter / FACT-1653 External Facts from PowerShell do not parse structured output (JSON/YAML) Change By: Geoff Nichols Assignee: Casey Williams Branan Riley 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-8140) NoMethodErrors involving Puppet::Face instances do not have a useful text representation
Title: Message Title Charlie Sharpsteen created an issue Puppet / PUP-8140 NoMethodErrors involving Puppet::Face instances do not have a useful text representation Issue Type: Bug Affects Versions: PUP 5.3.3, PUP 4.10.9 Assignee: Unassigned Created: 2017/11/09 10:18 AM Priority: Normal Reporter: Charlie Sharpsteen Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (FACT-1792) Backport platform fact acceptance test changes from 3.9.x -> 3.6.x
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1792 Backport platform fact acceptance test changes from 3.9.x -> 3.6.x Change By: Geoff Nichols Sprint: Platform OS Ready for Eng. 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-2189) The CRL can get corrupted if two workers revoke certs at same time
Title: Message Title Craig Gomes updated an issue Puppet / PUP-2189 The CRL can get corrupted if two workers revoke certs at same time Change By: Craig Gomes Sprint: Platform Core KANBAN Grooming Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1792) Backport platform fact acceptance test changes from 3.9.x -> 3.6.x
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1792 Backport platform fact acceptance test changes from 3.9.x -> 3.6.x Change By: Geoff Nichols Sprint: Platform OS Ready for Eng. 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-8136) refactor Puppet::Parameter.format so that we can avoid using %s in strings
Title: Message Title Henrik Lindberg commented on PUP-8136 Re: refactor Puppet::Parameter.format so that we can avoid using %s in strings no, it needs to change as well... I have not looked at code in detail - I was just suggesting use of lambda if that helps with registering a future formatting thing 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-2189) The CRL can get corrupted if two workers revoke certs at same time
Title: Message Title Justin Stoller commented on PUP-2189 Re: The CRL can get corrupted if two workers revoke certs at same time I assume we should move this out of the active sprint and into the backlog, since it looks like it needs to go back and be prioritized with other CA work? 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 Geoff Nichols updated an issue Facter / FACT-1792 Backport platform fact acceptance test changes from 3.9.x -> 3.6.x Change By: Geoff Nichols Sprint: Platform OS Grooming/Triage 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-3755) (maint) Optimize event queries with the latest_report? parameter
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3755 (maint) Optimize event queries with the latest_report? parameter Issue Type: Bug Assignee: Unassigned Created: 2017/11/09 9:00 AM Priority: Normal Reporter: gepetto-bot The original filter to get event counts from the latest report was SELECT * FROM (SELECT containing_class, SUM(CASE WHEN status = 'failure' THEN 1 ELSE 0 END) AS failures, SUM(CASE WHEN status = 'skipped' THEN 1 ELSE 0 END) AS skips, SUM(CASE WHEN (status = 'success' and coalesce(corrective_change, false) = false) THEN 1 ELSE 0 END) AS intentional_successes, SUM(CASE WHEN (status = 'success' and corrective_change = true) THEN 1 ELSE 0 END) AS corrective_successes, SUM(CASE WHEN (status = 'noop' and coalesce(corrective_change, false) = false) THEN 1 ELSE 0 END) AS intentional_noops, SUM(CASE WHEN (status = 'noop' and corrective_change = true) THEN 1 ELSE 0 END) AS corrective_noops FROM (SELECT DISTINCT certname, status, corrective_change, containing_class FROM (WITH inactive_nodes AS (SELECT certname FROM certnames WHERE (deactivated IS NOT NULL OR expired IS NOT NULL)) SELECT message AS message, old_value AS old_value, reports.receive_time AS report_receive_time, events.corrective_change AS corrective_change, containment_path AS containment_path, reports.certname AS certname, timestamp AS timestamp, reports.end_time AS run_end_time, reports.configuration_version AS configuration_version, new_value AS new_value, resource_title AS resource_title, status AS status, property AS property, resource_type AS resource_type, line AS line, environments.environment AS environment, containing_class AS containing_class, reports.start_time AS run_start_time, file AS file, encode(reports.hash::bytea, 'hex') AS report FROM resource_events events INNER JOIN reports ON events.report_id = reports.id LEFT JOIN environments ON reports.environment_id = environments.id WHERE ((encode(reports.hash::bytea, 'hex')) in ( SELECT
Jira (PUP-8136) refactor Puppet::Parameter.format so that we can avoid using %s in strings
Title: Message Title
Eric Delaney commented on PUP-8136
Re: refactor Puppet::Parameter.format so that we can avoid using %s in strings
Hmm. not sure that will work with the current format code:
def format(fmt, *args)
fmt % args.map { |arg| @sensitive ? "[redacted]" : arg.to_s }
end
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-8139) Spelling Error in Error Message
Title: Message Title Daniel Mcilhagga created an issue Puppet / PUP-8139 Spelling Error in Error Message Issue Type: Bug Assignee: Unassigned Created: 2017/11/09 7:52 AM Priority: Normal Reporter: Daniel Mcilhagga I have a customer who noticed the following spelling mistake: "To fix this, remove the certificate from both the master and the agent and then start a puppet run, which will automatically regenerate a certficate." This is found in: https://github.com/puppetlabs/pe-puppet/blob/08c4fbbdc7f82b7a6a3e1f10485dd6b5508665d6/lib/puppet/ssl/host.rb Add Comment
Jira (PUP-8128) Add URI data type
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-8128 Add URI data type Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8050) puppet agent -e environment
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-8050
puppet agent -e environment
Change By:
Henrik Lindberg
Release Notes Summary:
It is now possible to specify which environment to also use a short {{\-E}} flag (capital E) in addition to the long {{\--environment}} (which continues to work as before).
Release Notes:
New Feature
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8050) puppet agent -e environment
Title: Message Title Henrik Lindberg commented on PUP-8050 Re: puppet agent -e environment merged to 4.10.x 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-8050) puppet agent -e environment
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8050 puppet agent -e environment Change By: Henrik Lindberg Fix Version/s: PUP 4.10.z Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8102) Refactor PAL API, add 'call_function' and more to the PAL API
Title: Message Title Thomas Hallgren commented on PUP-8102 Re: Refactor PAL API, add 'call_function' and more to the PAL API Merged to feature_puppet-tasks at c43229c. 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-8102) Refactor PAL API, add 'call_function' and more to the PAL API
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8102 Refactor PAL API, add 'call_function' and more to the PAL API Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-8102) Refactor PAL API, add 'call_function' and more to the PAL API
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-8102 Refactor PAL API, add 'call_function' and more to the PAL API Change By: Thomas Hallgren Assignee: Henrik Lindberg Thomas Hallgren 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-8133) File_upload doesn’t work in a plan
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8133 File_upload doesn’t work in a plan Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-185) Add the execution functions from puppet to a bolt module
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet Task Runner / BOLT-185 Add the execution functions from puppet to a bolt module Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8133) File_upload doesn’t work in a plan
Title: Message Title Thomas Hallgren commented on PUP-8133 Re: File_upload doesn’t work in a plan Merged to feature_puppet-tasks at 552c8df. 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-8137) run_script function does not accept arguments
Title: Message Title Thomas Hallgren commented on PUP-8137 Re: run_script function does not accept arguments Merged to feature_puppet-tasks at ac4b22c. 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-8137) run_script function does not accept arguments
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8137 run_script function does not accept arguments Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-8138) Ruby true and false should be inferred to corresponding parameterized Boolean data type
Title: Message Title Thomas Hallgren commented on PUP-8138 Re: Ruby true and false should be inferred to corresponding parameterized Boolean data type Merged to master at 8206e7c. 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-8138) Ruby true and false should be inferred to corresponding parameterized Boolean data type
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-8138 Ruby true and false should be inferred to corresponding parameterized Boolean data type Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-8133) File_upload doesn’t work in a plan
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-8133 File_upload doesn’t work in a plan Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren 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-8137) run_script function does not accept arguments
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-8137
run_script function does not accept arguments
Change By:
Henrik Lindberg
Release Notes Summary:
It was not possible to use the {{run_script}} function because it did not accept any arguments and did not pass any on to the bolt executor. Instead it always resulted in an error. This is to now corrected and it is now possible to give a variable number of string arguments when calling can be given as a hash with a key {{ run_script 'arguments' }} holding an array of Strings . The default is an empty array. The string arguments may be any string, including empty strings.
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-8137) run_script function does not accept arguments
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-8137 run_script function does not accept arguments Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren 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-8132) Package Resource Always Uses -i Flag and Errors out if Already Installed
Title: Message Title Daniel Mcilhagga assigned an issue to Daniel Mcilhagga Puppet / PUP-8132 Package Resource Always Uses -i Flag and Errors out if Already Installed Change By: Daniel Mcilhagga Assignee: Daniel Mcilhagga 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-8138) Ruby true and false should be inferred to corresponding parameterized Boolean data type
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-8138 Ruby true and false should be inferred to corresponding parameterized Boolean data type Issue Type: Bug Assignee: Thomas Hallgren Created: 2017/11/09 1:48 AM Fix Versions: PUP 5.4.0 Priority: Normal Reporter: Thomas Hallgren This ticket addresses an oversight in the implementation of PUP-8117. The TypeCalculator should of course infer true to Boolean[true] and false to Boolean[false]. They are presently just inferred as Boolean Add Comment
Jira (PUP-8137) run_script function does not accept arguments
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-8137
run_script function does not accept arguments
Change By:
Henrik Lindberg
Release Notes Summary:
It was not possible to use the {{run_script}} function because it did not accept any arguments and did not pass any on to the bolt executor. Instead it always resulted in an error. This is to corrected and it is now possible to give a variable number of string arguments when calling {{run_script}}.
Sprint:
Tasks Kanban
Release Notes:
Bug Fix
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8137) run_script function does not accept arguments
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-8137 run_script function does not accept arguments Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8137) run_script function does not accept arguments
Title: Message Title Henrik Lindberg moved an issue Puppet / PUP-8137 run_script function does not accept arguments Change By: Henrik Lindberg Key: BOLT PUP - 212 8137 Project: Puppet Task Runner 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-212) run_script function does not accept arguments
Title: Message Title Henrik Lindberg created an issue Puppet Task Runner / BOLT-212 run_script function does not accept arguments Issue Type: Bug Assignee: Unassigned Created: 2017/11/09 1:26 AM Priority: Normal Reporter: Henrik Lindberg The run_script function does not accept arguments and does not pass anything on to the Bolt executor. As a result, any attempt to use run_script fails. The run_script function should accept a variable number of String arguments. The data type is String because the arguments are basically arguments as given on a command line and such can only be strings. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8020) Add data type Target to puppet for tasks/plans
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-8020
Add data type Target to puppet for tasks/plans
Change By:
Henrik Lindberg
Release Notes Summary:
A new data type {{Target}} has been added to the puppet type system to allow describing a 'target node' with a host string (a host name or complete URI) and a hash of options.It is recommended that plans that take parameters that are references to nodes/hosts should use this data type for parameters that accept one or more hosts; for example {{Target}}, or {{Array\[Target]}}.
Release Notes:
New Feature
Add Comment
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8020) Add data type Target to puppet for tasks/plans
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-8020 Add data type Target to puppet for tasks/plans Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8102) Refactor PAL API, add 'call_function' and more to the PAL API
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-8102
Refactor PAL API, add 'call_function' and more to the PAL API
Change By:
Henrik Lindberg
The PAL API should have a general {{call_function}}.The motivation for this was originally to be allow Bolt CLI to call {{run_task}}, but it seems better to allow calling any function. The API needs refactoring as the current implementation does not allow performing multiple operations without setting up the entire context for each call.There should also be methods for:* creating a new instance of a data type* creating a type instance* evaluating puppet logic
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-8102) Refactor PAL API, add 'call_function' and more to the PAL API
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8102 Refactor PAL API, add 'call_function' and more to the PAL API Change By: Henrik Lindberg Summary: Add a Refactor PAL API, add 'call_function' and more to the PAL API 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-8134) Don't reject tasks which specify sensitive parameters
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8134 Don't reject tasks which specify sensitive parameters Change By: Henrik Lindberg Release Notes Summary: It was not possible to use a task that used 'sensitive' metadata on a task parameter. This always led to an error. This field is now accepted in task metadata. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8134) Don't reject tasks which specify sensitive parameters
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-8134 Don't reject tasks which specify sensitive parameters Change By: Henrik Lindberg Assignee: Thomas Hallgren 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-8134) Don't reject tasks which specify sensitive parameters
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8134 Don't reject tasks which specify sensitive parameters Change By: Henrik Lindberg Fix Version/s: PUP 5.4.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-5987) Documentation for logdest is confusing
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5987 Documentation for logdest is confusing Change By: Henrik Lindberg Fix Version/s: PUP 4.10.z Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5987) Documentation for logdest is confusing
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5987 Documentation for logdest is confusing Change By: Henrik Lindberg Release Notes Summary: The documentation for the --logdest option now clearly shows that only an absolute path can be used when specifying a file log destination. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8136) refactor Puppet::Parameter.format so that we can avoid using %s in strings
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8136 refactor Puppet::Parameter.format so that we can avoid using %s in strings Change By: Henrik Lindberg Summary: refacter refactor Puppet::Parameter.format so that we can avoid using %s in strings 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-184) Add ability to generate Markdown
Title: Message Title Henrik Lindberg commented on PDOC-184 Re: Add ability to generate Markdown I googled if someone had already implemented this for yard, and there seems to be some attempts, but since we use special templates for the HTML, it is probably best if we develop a set of markdown templates for yard ourselves (could be quite a lot of work, but probably better than tweaking someone else's half baked approach; the one project I looked at was not finished/polished). 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-8134) Don't reject tasks which specify sensitive parameters
Title: Message Title Henrik Lindberg commented on PUP-8134 Re: Don't reject tasks which specify sensitive parameters If we allow rich-data to be present in the JSON given to scripts, the value would be in clear text in the output, but it would be wrapped in a pcore 'Sensitive' data type. This would allow it to be recognized as being sensitive and the reader must read that piece of json in a slightly different way in order to get the clear text value - both things are good since the script code must do the right thing with sensitive values (or error). If we do that, there is little use of the special "sensitive" meta data value - the same could then be achieved simply by giving the data type as Sensitive[T] instead of T + setting sensitive=true as meta data. That would then be the same as how it works in puppet in general. In UI etc. a test if a parameter is sensitive is simply an assignability test to Type[Sensitive] on the parameter's type. Some thought has to go into how to handle a Variant that involves a Sensitive - that is, if it is optional to give a sensitive value. 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-8136) refacter Puppet::Parameter.format so that we can avoid using %s in strings
Title: Message Title
Henrik Lindberg commented on PUP-8136
Re: refacter Puppet::Parameter.format so that we can avoid using %s in strings
Could this be done with giving a lambda to Param#format instead of a string? For example:
param.format(lambda() {|from, to| _("change from %{from_value} to %{to_value} failed: ") % { from_value: from, to_value
: to}}
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.
