Jira (PUP-8966) Windows security integration tests fail when the user does not have elevated rights
Title: Message Title
Glenn Sarti commented on PUP-8966
Re: Windows security integration tests fail when the user does not have elevated rights
Ahh ok...I think you meant running the spec tests in Puppet require elevation. Might need to put a fail('Spec tests require elevation') or similar in the security_spec file.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8567) Extract augeas type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8567 Extract augeas type/provider into a module Change By: Josh Cooper Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8567) Extract augeas type/provider into a module
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8567 Extract augeas type/provider into a module Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8966) Windows security integration tests fail when the user does not have elevated rights
Title: Message Title Glenn Sarti commented on PUP-8966 Re: Windows security integration tests fail when the user does not have elevated rights Ethan Brown We explicity support this according to our docs. https://puppet.com/docs/pe/2018.1/installing/installing_agents.html#run-windows-agents-without-admin-privileges Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-630) PowerShell based tasks throw an error about a non-existant parameter
Title: Message Title
Glenn Sarti updated an issue
Puppet Task Runner / BOLT-630
PowerShell based tasks throw an error about a non-existant parameter
Change By:
Glenn Sarti
A user on Slack reported that they were unable to use the WSUS Client tasks because they were getting the following error;{code}Started on localhost...Failed on localhost: The task failed with exit code 1: $private:taskArgs = Get-ContentAsJson ( : System.Management.Automation.ParameterBindingException: A parameter cannot be found that matches parameter name '_task'. at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception) at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException { }Failed on 1 node: winrm://localhost{code}I know that those tasks worked fine in Bolt 0.20.5 as that's when I authored them. That error is not within the task itself but within Bolt and is probable related to https://github.com/puppetlabs/bolt/commit/9bc85d7a18fdb7d1e7e844c376bb5f42a59cdcedI have marked this as major as I very strongly suspect all PowerShell based tasks , using cmdlet binding (Which is recommended), will now be failing.
Add Comment
Jira (BOLT-630) PowerShell based tasks throw an error about a non-existant parameter
Title: Message Title Glenn Sarti commented on BOLT-630 Re: PowerShell based tasks throw an error about a non-existant parameter Repro: Clone the wsus_client module Install bolt 0.21.0 (via chocolatey) Ensure local WinRM connections are enabled Run bolt against the local machine with the wsus_client::update_history task Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-630) PowerShell based tasks throw an error about a non-existant parameter
Title: Message Title
Glenn Sarti updated an issue
Puppet Task Runner / BOLT-630
PowerShell based tasks throw an error about a non-existant parameter
Change By:
Glenn Sarti
Summary:
{module PowerShell based tasks throw an error about a non - name} : {brief summary of issue} existant parameter
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-630) {module-name} : {brief summary of issue}
Title: Message Title
Glenn Sarti created an issue
Puppet Task Runner / BOLT-630
{module-name} : {brief summary of issue}
Issue Type:
Bug
Affects Versions:
BOLT 0.21.0
Assignee:
Unassigned
Created:
2018/06/27 6:47 PM
Environment:
Windows 10 - 1803 Bolt 0.21.0 PowerShell 5.1
Priority:
Major
Reporter:
Glenn Sarti
A user on Slack reported that they were unable to use the WSUS Client tasks because they were getting the following error;
Started on localhost...
Failed on localhost:
The task failed with exit code 1:
$private:taskArgs = Get-ContentAsJson (
:
Jira (PUP-8846) Extract the code & verify the module
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8846 Extract the code & verify the module Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8573) Extract macdslocal type/provider into a module
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8573 Extract macdslocal type/provider into a module Change By: Josh Cooper Sprint: Platform Core Hopper KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8573) Extract macdslocal type/provider into a module
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8573 Extract macdslocal type/provider into a module Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7433) Restructure Gemfile to use different group names
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7433 Restructure Gemfile to use different group names Change By: Josh Cooper Team: Platform Core Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3942) Add travis testing for newer jdk to see what happens...
Title: Message Title Austin Blatt commented on PDB-3942 Re: Add travis testing for newer jdk to see what happens... I tracked the error as far as our use of (ns/find-namespaces-on-classpath) inside cli-namespaces. The ns/find-namespaces-on-classpath) function has been deprecated since Clojure 1.3. My initial thought is this is most likely in relation to the changed type of the Application ClassLoader. The application class loader is no longer an instance of java.net.URLClassLoader (an implementation detail that was never specified in previous releases). Code that assumes that ClassLoader::getSytemClassLoader returns a URLClassLoader object will need to be updated. Note that Java SE and the JDK do not provide an API for applications or libraries to dynamically augment the class path at run-time. See Java 9 release notes for more info (http://www.oracle.com/technetwork/java/javase/9-relnote-issues-3704069.html). We should instead use java.classpath or see if we can use kitchensink. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) --
Jira (BOLT-614) I want to know how to write multi-implementation tasks so they are backwards compatible with PE 2018.1
Title: Message Title Thomas Kishel commented on BOLT-614 Re: I want to know how to write multi-implementation tasks so they are backwards compatible with PE 2018.1 Bolt docs state that "a task can also have multiple implementation (sic)" and "This information about writing tasks applies for both Puppet Enterprise and Bolt" but in 2018.1.2 ... [root@pe-201812-master ~]# puppet task show example puppetlabs.orchestrator.task/invalid-task: Task example includes multiple matching task files Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com.
Jira (BOLT-624) Update homebrew-puppet (Bolt 0.21.1)
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-624 Update homebrew-puppet (Bolt 0.21.1) Change By: Michael Smith Assignee: Lucy Wyman Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3942) Add travis testing for newer jdk to see what happens...
Title: Message Title Austin Blatt commented on PDB-3942 Re: Add travis testing for newer jdk to see what happens... On Java 10, I get the following failures. lein test puppetlabs.puppetdb.core-test lein test :only puppetlabs.puppetdb.core-test/jdk-fail-message FAIL in (jdk-fail-message) (core_test.clj:73) No unsupported message when using 1.7 expected: (false? (clojure.core/deref fail?)) actual: (not (false? true)) lein test :only puppetlabs.puppetdb.core-test/jdk-fail-message FAIL in (jdk-fail-message) (core_test.clj:89) fail message appears in log and stdout when using JDK 1.6
Jira (PUP-8969) Sensitive parameters are not redacted from reports / agent output when used in templates
Title: Message Title
Josh Cooper commented on PUP-8969
Re: Sensitive parameters are not redacted from reports / agent output when used in templates
Capturing additional comments. Ethan Brown recommended moving the sensitive data into a different file. The script can be managed as a normal file, and diffs displayed, while the sensitive data file content could be marked as sensitive:
file {'/tmp/test1':
ensure => file,
content => template('sensitive/test1.erb'),
}
file {'/tmp/credentials':
ensure => file,
owner => '...',
group => '...',
mode => '0600',
content => Sensitive($credentials),
}
Jira (BOLT-581) Evaluate top 100 modules
Title: Message Title Michael Smith commented on BOLT-581 Re: Evaluate top 100 modules How many use bare facts or are all facts accessed through $::facts? Only two uses $::facts. 14 modules use $facts. Bare facts are much more common. How many include providers? ~40 How many include types? Most of those also include types. Which core types and providers are most common? How many modules just use File/Service/Exec? How many include non-autoloader manifests? IE something other than a class or defined type at top scope. Are these even allowed in puppet 6. What facts to they use? What facts do they use for provider suitability? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-581) Evaluate top 100 modules
Title: Message Title
Michael Smith commented on BOLT-581
Re: Evaluate top 100 modules
Downloaded with
curl https://forgeapi.puppet.com:443/v3/modules\?sort_by\=downloads\\=100\_requirement\=%3E%3D3.0.0
Quick summary can be grabbed with jq
jq '.results[] | {slug: .slug, downloads: .downloads}
Download them all with
jq -r '.results[].current_release.file_uri' | xargs -I{} curl -O https://forgeapi.puppet.com:443{}
Add Comment
Jira (PUP-8970) Puppet cron acceptance tests should be skipped on Fedora 28
Title: Message Title Casey Williams created an issue Puppet / PUP-8970 Puppet cron acceptance tests should be skipped on Fedora 28 Issue Type: Task Assignee: Casey Williams Created: 2018/06/27 3:04 PM Fix Versions: PUP 5.5.z Labels: systemd cron type_and_provider fedora linux Priority: Normal Reporter: Casey Williams Fedora 28 does not ship with a crontab executable preinstalled (I assume that systemd timers are now the preferred way to handle scheduled tasks). This fails puppet's cron acceptance tests. Add Comment
Jira (BOLT-581) Evaluate top 100 modules
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-581 Evaluate top 100 modules Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2700) Migrate to trapperkeeper testutils/logging
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-2700 Migrate to trapperkeeper testutils/logging Change By: Austin Blatt Release Notes Summary: Only changes to dev tests Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8942) Support issuing certificates with IP Address Subject Alternative Names
Title: Message Title
Amy Lazarte updated an issue
Puppet / PUP-8942
Support issuing certificates with IP Address Subject Alternative Names
Change By:
Amy Lazarte
Comment:
I think it should be {code:java}puppet cert generate --dns-alt-names DNS:alt1.example.com,alt2.example.com,IP:203.0.113.1{code} without the equals sign. The puppet cert list -a output looks like {code:java}+ "localhost" (altnames: "DNS:alt1.example.com", "DNS:alt2.example.com", "IP Address:203.0.113.1"){code}I think, although I'll look into that to confirm.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7407) Add deprecation warning to Puppet::Util.absolute_path?
Title: Message Title Josh Cooper commented on PUP-7407 Re: Add deprecation warning to Puppet::Util.absolute_path? After digging into this more, it looks like we have to preserve the existing implementation and do a docs only deprecation. The problem is that the absolute_path? method serves multiple purposes and it's hard to tell which from within the method. Sometimes it's used on the agent (in a type/provider) to validate that a parameter/property is an absolute path. This is common in puppet, and it would be better for custom types/provider to just use ruby to do this, e.g. Pathname.new(path).absolute?. Functions also use the method to validate paths. For example, stdlib has a deprecated function is_absolute_path, which calls the 3x version of the is_absolute_path function, which calls puppet's absolute_path? method. Since the compiler doesn't know whether it's compiling for a windows or unix node, the function verifies that it's an absolute path for either windows or unix, but it doesn't know exactly which. This can lead to false positives as /foo is absolute on unix, but not windows. With the introduction of puppet data types, it's better to do match values against the specific path data type: 'C:\foo' =~ Stdlib::Windowspath '/foo' =~ Stdlib::Unixpath See https://github.com/puppetlabs/puppetlabs-stdlib/blob/master/types/unixpath.pp and https://github.com/puppetlabs/puppetlabs-stdlib/blob/master/types/windowspath.pp. There is also https://github.com/puppetlabs/puppetlabs-stdlib/blob/master/types/absolutepath.pp for the generic "is it unix or windows path" case. Add Comment
Jira (PUP-8942) Support issuing certificates with IP Address Subject Alternative Names
Title: Message Title Amy Lazarte commented on PUP-8942 Re: Support issuing certificates with IP Address Subject Alternative Names I think it should be puppet cert generate --dns-alt-names DNS:alt1.example.com,alt2.example.com,IP:203.0.113.1 without the equals sign. The rest looks good to me. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8942) Support issuing certificates with IP Address Subject Alternative Names
Title: Message Title Garrett Guillotte commented on PUP-8942 Re: Support issuing certificates with IP Address Subject Alternative Names Is this an accurate example for docs, based on the unit test contents? To configure alternative names, add this configuration setting to your certificate authority (CA) server's puppet.conf for certificate requests: :dns_alt_names => 'DNS:alt1.example.com, alt2.example.com, IP: 203.0.113.1' and run this command from your CA server's command line when generating certificates: puppet cert generate --dns-alt-names=DNS:alt1.example.com,alt2.example.com,IP:203.0.113.1 You can confirm the configured alternative names by running puppet cert list -a from your CA server: (alt names: ["DNS:alt1.example.com", "DNS:alt2.example.com", "IP Address:203.0.113.1"]) I'm least certain about the puppet cert list -a output. Add Comment
Jira (BOLT-629) Stacktrace when 'nodes' in inventory group is not an array
Title: Message Title Michael Smith commented on BOLT-629 Re: Stacktrace when 'nodes' in inventory group is not an array In general yes. We also get weird errors if vars and facts are not hashes, and if features is not an array. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7407) Add deprecation warning to Puppet::Util.absolute_path?
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7407 Add deprecation warning to Puppet::Util.absolute_path? Change By: Josh Cooper Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-629) Stacktrace when 'nodes' in inventory group is not an array
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-629 Stacktrace when 'nodes' in inventory group is not an array Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-629) Stacktrace when 'nodes' in inventory group is not an array
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-629 Stacktrace when 'nodes' in inventory group is not an array Issue Type: Bug Assignee: Unassigned Created: 2018/06/27 1:27 PM Priority: Normal Reporter: Alex Dreyer We need to perform some validation before groups objects are created to present better errors to users. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8965) Change dns-alt-names option to subject-alt-names
Title: Message Title Garrett Guillotte updated an issue Puppet / PUP-8965 Change dns-alt-names option to subject-alt-names Change By: Garrett Guillotte Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-594) POC apply keyword
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-594 POC apply keyword Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1832) Facter Fails on Solaris 11.3 Patch 29.0.4.0 Native Zone.
Title: Message Title Branan Riley updated an issue Facter / FACT-1832 Facter Fails on Solaris 11.3 Patch 29.0.4.0 Native Zone. Change By: Branan Riley Labels: customer solaris virtualization Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8969) Sensitive parameters are not redacted from reports / agent output when used in templates
Title: Message Title Erik Hansen commented on PUP-8969 Re: Sensitive parameters are not redacted from reports / agent output when used in templates Josh Cooper - what I was expecting from the sensitive type is that the whole of the diff output would not be redacted, but only the sensitive string from within the diff. Maybe this is more of a feature request, but I think there's an assumption that the Sensitive type should be respected everywhere in Puppet (and if it isn't we should document where Sensitive param values would be exposed) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-623) Kick off release pipeline (Bolt 0.21.1)
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-623 Kick off release pipeline (Bolt 0.21.1) Change By: Michael Smith Assignee: Lucy Wyman Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-620) I want to see a backtrace when bolt errors
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-620 I want to see a backtrace when bolt errors Change By: Kate Lopresti Labels: docs-reviewed feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1832) Facter Fails on Solaris 11.3 Patch 29.0.4.0 Native Zone.
Title: Message Title Branan Riley updated an issue Facter / FACT-1832 Facter Fails on Solaris 11.3 Patch 29.0.4.0 Native Zone. Change By: Branan Riley Fix Version/s: FACT 3.11.3 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-591) Generated templated output for strings docs
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-591 Generated templated output for strings docs Change By: Michael Smith Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-591) Generated templated output for strings docs
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-591 Generated templated output for strings docs Change By: Michael Smith Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-622) Reconcile git commits, JIRA tickets, and versions (Bolt 0.21.1)
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-622 Reconcile git commits, JIRA tickets, and versions (Bolt 0.21.1) Change By: Michael Smith Assignee: Lucy Wyman Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-616) Add 'features' to targets in inventory
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-616 Add 'features' to targets in inventory Change By: Michael Smith Labels: docs docs -reviewed feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-617) Include net-ssh-krb in the puppet-bolt package
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-617 Include net-ssh-krb in the puppet-bolt package Change By: Kate Lopresti Labels: docs-reviewed feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8969) Sensitive parameters are not redacted from reports / agent output when used in templates
Title: Message Title Josh Cooper assigned an issue to Erik Hansen Puppet / PUP-8969 Sensitive parameters are not redacted from reports / agent output when used in templates Change By: Josh Cooper Assignee: Erik Hansen Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8969) Sensitive parameters are not redacted from reports / agent output when used in templates
Title: Message Title
Reid Vandewiele commented on PUP-8969
Re: Sensitive parameters are not redacted from reports / agent output when used in templates
I added a PR which I think clarifies the current limitations of Sensitive. It might make sense to break this ticket up into two, if I understand the problem correctly. 1: Provide a kind of Sensitive interpolation, wherein you can create a new Sensitive string by interpolating non-sensitive Strings and Sensitive Strings, where the end result should be a Sensitive string with a context-sensitive redacted print value. E.g. let something like Sensitive("safe text ${sensitive} more safe text") print as safe text [redacted] more safe text. 2: Make the show_diff operation of the File resource respect Sensitive types
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8969) Sensitive parameters are not redacted from reports / agent output when used in templates
Title: Message Title
Josh Cooper commented on PUP-8969
Re: Sensitive parameters are not redacted from reports / agent output when used in templates
If you wrap the template as Sensitive, then it works as expected for me:
file {'/tmp/test1':
ensure => present,
content => Sensitive(template('sensitive/test1.erb')),
}
file {'/tmp/test2':
ensure => present,
content => Sensitive(template('sensitive/test2.epp')),
}
Note redacting sensitive file content was fixed in PUP-6627:
$ touch /tmp/test{1,2}
$ bx puppet apply -e "include sensitive" --modulepath ~/work/modules --show_diff
Notice: Compiled catalog for
Jira (BOLT-616) Add 'features' to targets in inventory
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-616 Add 'features' to targets in inventory Change By: Kate Lopresti Labels: docs-reviewed feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-616) Add 'features' to targets in inventory
Title: Message Title Michael Smith commented on BOLT-616 Re: Add 'features' to targets in inventory Error cases don't display particularly helpful messages, but that is true for facts and vars as well. We should improve that independent of this ticket. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-628) Update Winston bolt ticket creation
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-628 Update Winston bolt ticket creation Issue Type: Improvement Assignee: Unassigned Created: 2018/06/27 11:31 AM Priority: Normal Reporter: Lucy Wyman There are a few issues with Winston ticket creation to address: It doesn't link the Bolt tickets to the RE tickets. This might be a permissions issue, or an issue with our ticket creating. Set the team to be "Bolt" instead of "Direct change" Remove Bolt subteam Set the sprint to be bolt-kanban Add Comment
Jira (PUP-8959) FastGettext.default_text_domain order dependent test failure
Title: Message Title Michael Smith commented on PUP-8959 Re: FastGettext.default_text_domain order dependent test failure Put up a PR to fix the thing Josh found. Not sure it's sufficient, as I haven't reproduced the original error message. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-583) Unable to use "localhost" as a node on Windows
Title: Message Title Kate Lopresti updated an issue Puppet Task Runner / BOLT-583 Unable to use "localhost" as a node on Windows Change By: Kate Lopresti Labels: docs-reviewed resolved-issue-added Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8947) Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type
Title: Message Title Gene Liverman commented on PUP-8947 Re: Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type Gotcha Reid Vandewiele. With much help from others, I also realized the hiera side of this is doable via a regex on key names like so in common.yaml: --- lookup_options: '^profile::.+::sensitive_\w+$': convert_to: 'Sensitive' # that would cover keys like this: profile::some_web_app::sensitive_db_password: ENC[PKCS7,] # and would skip keys like this: profile::some_web_app::table_of_sensitive_stuff_name: 'foo' Learning this makes me feel better about the idea of PUP-8946 not being done.
Jira (PUP-8959) FastGettext.default_text_domain order dependent test failure
Title: Message Title Michael Smith commented on PUP-8959 Re: FastGettext.default_text_domain order dependent test failure I can fix the particular failure Josh found. Trying to track down how the original failure happens because that code path should ensure there's a default text domain setup. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-556) Submit puppet-specifications PR for multi-file tasks
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-556 Submit puppet-specifications PR for multi-file tasks Change By: Cas Donoghue Assignee: Cas Donoghue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8947) Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type
Title: Message Title Reid Vandewiele commented on PUP-8947 Re: Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type Gene Liverman yep, understood. My concern for customers is not that new behavior would be default, but that the opt-in toggle is a massive one. When toggled on, all lookups of all values coming from the eyaml backend become Sensitive. Because of the bolded point above, a Sensitive is NOT interchangeable with a String, this means that a huge uplift and preparation in Puppet code is required in preparation for that toggle being turned. It's not reasonable to ask most customers to do that, which means either slow adoption or constrained adoption of that feature. If we instead make it so that if a customer wants a string input to be Sensitive they make their class parameter type Sensitive, that's something they can do and adopt in small, iterative steps. Same or similar end value (you easily have Sensitive when you need it), and effectively no upfront cost for adoption. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8947) Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type
Title: Message Title Gene Liverman commented on PUP-8947 Re: Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type Reid Vandewiele fwiw, I assumed PUP-8946 would be a toggle, not a default, as I think was already talked about in that ticket. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8959) FastGettext.default_text_domain order dependent test failure
Title: Message Title Michael Smith commented on PUP-8959 Re: FastGettext.default_text_domain order dependent test failure So maybe we need Puppet::GettextConfig.create_default_text_domain in the after(:each) block of those tests? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-627) Secure password prompt windows
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-627 Secure password prompt windows Change By: Michael Smith Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-627) Secure password prompt windows
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-627 Secure password prompt windows Issue Type: Bug Affects Versions: Bolt 0.21.0 Assignee: Unassigned Created: 2018/06/27 10:12 AM Priority: Normal Reporter: Cas Donoghue On windows (win-10-1803-x86_64) when --password or -p is left blank, a Bad file descriptor (Errno::EBADF) occurs before secure password prompt. C:\cygwin64\home\Administrator>bolt --version bolt --version 0.21.0 C:\cygwin64\home\Administrator>bolt command run whoami --nodes pq0rvm2ltgyn2mi.delivery.puppetlabs.net --transport winrm --no-ssl --user Administrator --password
Jira (PUP-8961) Asa Puppet developer I would like to be able to use scripts in the TASKS module file in the a source for puppet resources so has to not maintain code twice
Title: Message Title Michael Smith commented on PUP-8961 Re: Asa Puppet developer I would like to be able to use scripts in the TASKS module file in the a source for puppet resources so has to not maintain code twice We also plan to add some improvements to task runners soon that should make it possible to share library code between tasks and providers. BOLT-556 tracks the initial spec work. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6729) NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators
Title: Message Title Erick Banks updated an issue Puppet / PUP-6729 NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators Change By: Erick Banks Sprint: Windows 2018-06-13, Windows 2018-06-27 , Windows 2018-07-05 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8947) Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type
Title: Message Title Reid Vandewiele commented on PUP-8947 Re: Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type I would be concerned that PUP-8946 would have a much higher adoption cost for an organization when compared to this ticket, PUP-8947. It sounds exciting to just have all values from a given backend, eyaml, returned as Sensitive, but as Henrik already mentioned that would break existing users pretty hard. A Sensitive is NOT interchangeable with a String. Users writing code who aren't being intentional about Sensitive type usage would easily be surprise, and their code would easily break, if Sensitive values are returned by a backend unexpectedly. Going the route instead of making CPL more intelligent allows class authors to specify the kind of type they want and treat it accordingly in their code without needing to assert or know what kind of Hiera backend the data will be coming from. We should accept this feature request. This solution allows piecemeal adoption. A whole-backend conversion to Sensitive does not. If we implement intelligent CPL that does casting to Sensitive when necessary, we won't need the all-or-nothing alternative. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (BOLT-621) Bolt 0.21.1 2018-06-27 Release
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-621 Bolt 0.21.1 2018-06-27 Release Change By: Lucy Wyman Sub-team: Bolt Team: Direct Change Bolt Sprint: Bolt Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-626) Send release announcements (Bolt 0.21.1)
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-626 Send release announcements (Bolt 0.21.1) Issue Type: Sub-task Assignee: Kate Lopresti Created: 2018/06/27 9:32 AM Due Date: 2018/06/27 Priority: Normal Reporter: Lucy Wyman (Initial planned release date: 2018-06-27) Once docs have finished building (check that all links resolve appropriately) - Send the announcement pasted by Kate Lopresti to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and d...@puppet.com (all separately). You must be a member of these groups in order to send. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. If you want, make a PSA on IRC and/or Slack, something along the lines of "PSA: Bolt 0.21.1 is now available". Add Comment
Jira (BOLT-624) Update homebrew-puppet (Bolt 0.21.1)
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-624 Update homebrew-puppet (Bolt 0.21.1) Issue Type: Sub-task Assignee: Lucy Wyman Created: 2018/06/27 9:32 AM Due Date: 2018/06/27 Priority: Normal Reporter: Lucy Wyman (Initial planned release date: 2018-06-27) Until we automate this, you'll also need to update the version and SHA hashes of https://github.com/puppetlabs/homebrew-puppet/blob/master/Casks/puppet-bolt.rb. To do this please Create a fork of the homebrew-puppet repo Create a new branch on that fork Update the version to the new version in https://github.com/puppetlabs/homebrew-puppet/blob/master/Casks/puppet-bolt.rb Download the `puppet-bolt-latest.dmg` from http://downloads.puppetlabs.com/mac/10.13/PC1/x86_64/, http://downloads.puppetlabs.com/mac/10.12/PC1/x86_64/, and http://downloads.puppetlabs.com/mac/10.11/PC1/x86_64/ Calculate the SHA256 hash of each `.dmg` package by running `shasum -a 256 ` Update the sha hashes in the file linked above Put up a PR to homebrew-puppet and request review
Jira (BOLT-625) Docs for bolt release (Bolt 0.21.1)
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-625 Docs for bolt release (Bolt 0.21.1) Issue Type: Sub-task Assignee: Kate Lopresti Created: 2018/06/27 9:32 AM Due Date: 2018/06/27 Priority: Normal Reporter: Lucy Wyman (Initial planned release date: 2018-06-27) Release notes and docs changes for bolt 0.21.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-623) Kick off release pipeline (Bolt 0.21.1)
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-623 Kick off release pipeline (Bolt 0.21.1) Issue Type: Sub-task Assignee: Lucy Wyman Created: 2018/06/27 9:31 AM Due Date: 2018/06/27 Priority: Normal Reporter: Lucy Wyman (Initial planned release date: 2018-06-27) With our shiny new automated builds pipeline, all you have to do is Go to https://jenkins-master-prod-1.delivery.puppetlabs.net/view/bolt/job/platform_bolt-vanagon_bolt-release-init_bolt-release/ Click "Build with Parameters" Check the PUBLIC checkbox Enter the version in the NEW_TAG box (x.y.z format) Click build! And make sure the pipeline is green! Add Comment
Jira (BOLT-622) Reconcile git commits, JIRA tickets, and versions (Bolt 0.21.1)
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-622 Reconcile git commits, JIRA tickets, and versions (Bolt 0.21.1) Issue Type: Sub-task Assignee: Lucy Wyman Created: 2018/06/27 9:31 AM Due Date: 2018/06/27 Priority: Normal Reporter: Lucy Wyman (Initial planned release date: 2018-06-27) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=Bolt and fixVersion="Bolt x.y.z"' in JIRA. Add Comment
Jira (BOLT-621) Bolt 0.21.1 2018-06-27 Release
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-621 Bolt 0.21.1 2018-06-27 Release Issue Type: Task Assignee: Lucy Wyman Created: 2018/06/27 9:31 AM Priority: Normal Reporter: Lucy Wyman Bolt 0.21.1 2018-06-27 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-616) Add 'features' to targets in inventory
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-616 Add 'features' to targets in inventory Change By: Alex Dreyer Release Notes Summary: Features for targets can now be stored in the inventory file. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-583) Unable to use "localhost" as a node on Windows
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-583 Unable to use "localhost" as a node on Windows Change By: Cas Donoghue Release Notes Summary: Do not default to local transport when targeting localhost on windows. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-616) Add 'features' to targets in inventory
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-616 Add 'features' to targets in inventory Change By: David Kramer Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-616) Add 'features' to targets in inventory
Title: Message Title David Kramer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-616 Add 'features' to targets in inventory Change By: David Kramer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-591) Generated templated output for strings docs
Title: Message Title David Kramer assigned an issue to Michael Smith Puppet Task Runner / BOLT-591 Generated templated output for strings docs Change By: David Kramer Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-620) I want to see a backtrace when bolt errors
Title: Message Title Michael Smith commented on BOLT-620 Re: I want to see a backtrace when bolt errors Added at https://github.com/puppetlabs/bolt/pull/494. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8966) Windows security integration tests fail when the user does not have elevated rights
Title: Message Title Ethan Brown commented on PUP-8966 Re: Windows security integration tests fail when the user does not have elevated rights Puppet requires elevation, so this is expected behavior. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3953) Update pdbext to clj-parent 2.0 and clojure 1.9
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3953 Update pdbext to clj-parent 2.0 and clojure 1.9 Change By: Rob Browning Release Notes Summary: PuppetDB has migrated to Clojure 1.9. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-583) Unable to use "localhost" as a node on Windows
Title: Message Title Cas Donoghue commented on BOLT-583 Re: Unable to use "localhost" as a node on Windows Testing: On linux: --nodes localhost uses local transport over default/provided cas@cas-ThinkPad-T460p:~/working_dir/bolt$ bolt command run whoami --nodes localhost --transport winrm Started on localhost... Finished on localhost: STDOUT: cas Successful on 1 node: localhost Ran on 1 node in 0.00 seconds On windows: --nodes uses default transport (or transport specified) C:\cygwin64\home\Administrator\bolt>bundle exec bolt command run whoami --nodes localhost --no-host-key-check bundle exec bolt command run whoami --nodes localhost --no-host-key-check Started on localhost...
Jira (PUP-8969) Sensitive parameters are not redacted from reports / agent output when used in templates
Title: Message Title Erik Hansen created an issue Puppet / PUP-8969 Sensitive parameters are not redacted from reports / agent output when used in templates Issue Type: Bug Affects Versions: PUP 5.5.2 Assignee: Unassigned Created: 2018/06/27 8:50 AM Priority: Normal Reporter: Erik Hansen Description: When I use the sensitive data type I expect it to be treated as sensitive when used in templates. However it is not. Steps to reproduce: I've created a small module / repro case here: https://github.com/suckatrash/sensitive Just apply the class "sensitive" Actual Results: If I declare the class "sensitive" it will create two test files /test1 and /test2. If I make any changes in the files and run puppet again, I'll see: +This string should be redacted: 'this is sensitive' in the output of the puppet run and in the report. If I don't unwrap the sensitive parameter and use the commented line in one of the templates I'll see this: +This string should be redacted: 'Sensitive [value redacted]'
Jira (PUP-8969) Sensitive parameters are not redacted from reports / agent output when used in templates
Title: Message Title Erik Hansen updated an issue Puppet / PUP-8969 Sensitive parameters are not redacted from reports / agent output when used in templates Change By: Erik Hansen Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8942) Support issuing certificates with IP Address Subject Alternative Names
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8942 Support issuing certificates with IP Address Subject Alternative Names Change By: Maggie Dreyer Release Notes Summary: Users can now use IP addresses for the dns-alt-names options and settings . DNS subject alternative names should be prefixed with "DNS:" while IP names should be prefixed with "IP:". Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-620) I want to see a backtrace when bolt errors
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-620 I want to see a backtrace when bolt errors Change By: Alex Dreyer Release Notes Summary: Bolt now supports a --trace option which will cause it to print a backtrace before exiting after an exception Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-620) I want to see a backtrace when bolt errors
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-620 I want to see a backtrace when bolt errors Change By: Alex Dreyer Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-620) I want to see a backtrace when bolt errors
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-620 I want to see a backtrace when bolt errors Issue Type: Story Assignee: Unassigned Created: 2018/06/27 8:19 AM Priority: Normal Reporter: Alex Dreyer Bolt should accept a --trace option to make it easier for the bolt team to debug issues and get more information in user bug reports. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8947) Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type
Title: Message Title Gene Liverman commented on PUP-8947 Re: Automatically cast to Sensitive when returning a string to a lookup for a Sensitive type Josh Cooper I don't think this ticket and PUP-8946 are mutually exclusive. The other one is the one I am most excited about but I think this one would provide real value also. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8961) Asa Puppet developer I would like to be able to use scripts in the TASKS module file in the a source for puppet resources so has to not maintain code twice
Title: Message Title Adam Buxton commented on PUP-8961 Re: Asa Puppet developer I would like to be able to use scripts in the TASKS module file in the a source for puppet resources so has to not maintain code twice https://tickets.puppetlabs.com/browse/DOCUMENT-880 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8962) Type and provider info should be logged when prefetch fails
Title: Message Title Neil Binney updated an issue Puppet / PUP-8962 Type and provider info should be logged when prefetch fails Change By: Neil Binney CS Priority: Needs Priority Reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8956) puppet agent doesn't run properly when avast anti-virus running
Title: Message Title Neil Binney updated an issue Puppet / PUP-8956 puppet agent doesn't run properly when avast anti-virus running Change By: Neil Binney CS Priority: Needs Priority Reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8900) "puppet facts upload" face only tries first master in server_list
Title: Message Title Neil Binney updated an issue Puppet / PUP-8900 "puppet facts upload" face only tries first master in server_list Change By: Neil Binney CS Priority: Needs Priority Reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8957) [Regression] PUP-8167 behaviour noted in Puppet AiO 5.5.3
Title: Message Title Neil Binney updated an issue Puppet / PUP-8957 [Regression] PUP-8167 behaviour noted in Puppet AiO 5.5.3 Change By: Neil Binney CS Priority: Needs Priority Reviewed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8710) Smarter cached catalogs
Title: Message Title Neil Binney updated an issue Puppet / PUP-8710 Smarter cached catalogs Change By: Neil Binney CS Priority: Normal CS Impact: There is a workaround where facts can be uploaded, but requires some configuration to get working.With the agent running in cron run facts locally on the agent and compare against threshold, If the threshold has not been breached the agent can continue to run against the cached catalog.Increasing compile masters in the setup would be recommend to handle additional load rather than relying on cached catalogs.It it a good idea but would require considerable update to the Puppet Agent. further user cases will be needed to make business case for this feature to be resourced. Number of large scale customers using cached catalogs is quite low. CS Severity: 2 - Annoyance CS Business Value: 2 - $$$ CS Frequency: 1 - 1-5% of Customers Add Comment This message was sent by Atlassian JIRA
Jira (PUP-8900) "puppet facts upload" face only tries first master in server_list
Title: Message Title Jesse Reynolds updated an issue Puppet / PUP-8900 "puppet facts upload" face only tries first master in server_list Change By: Jesse Reynolds CS Priority: Needs Priority Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8961) Asa Puppet developer I would like to be able to use scripts in the TASKS module file in the a source for puppet resources so has to not maintain code twice
Title: Message Title Adam Buxton commented on PUP-8961 Re: Asa Puppet developer I would like to be able to use scripts in the TASKS module file in the a source for puppet resources so has to not maintain code twice Nice, I’ll raise docs ticket as it appears to be undocumented? https://puppet.com/docs/puppet/5.5/file_serving.html Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
