Jira (PUP-8395) Exec Parity for Windows
Title: Message Title Paul Anderson updated an issue Puppet / PUP-8395 Exec Parity for Windows Change By: Paul Anderson In Linux, Puppet typically runs as root (full privileges) and can leverage the exec resource's user parameter to run a command as a local user. In Windows, this parity is lacking and it's increasingly causing problems for Puppet users. It would be nice to run things as a local user.This issue is further compounded by common Microsoft System Administration use cases, where various pieces of software are installed and run as domain service accounts. For instance, the SQL Server module does it with [some gnarly Ruby in a provider to set domain credentials in 3 places | https://github.com/puppetlabs/puppetlabs-sqlserver/blob/master/lib/puppet/provider/sqlserver_features/mssql.rb#L7 -L8 ] by passing parameters to the installer. I suggest writing a custom installation provider for software requiring a service account is not a reasonable ask for a typical user who is an experienced Windows admin and nascent Puppet practitioner.There is a large and growing amount of Microsoft enterprise software (SQL Server, SCOM, SCCM, SCVMM) that recommends or requires the use of a domain service account, and there's not currently a good way to address it. Feature parity (and perhaps going a little further to support Domain Accounts) would be a good start, especially if this exec allows users to get the automation done while we determine if other features are needed. (For instance, passing a Microsoft Domain user credential to the package resource).Finally, field experience indicates this is complicated further by Mandatory Access Controls. These may limit the ability of any service running as Local System to interact with the wider world using domain credentials. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PUP-8395) Exec Parity for Windows
Title: Message Title Paul Anderson created an issue Puppet / PUP-8395 Exec Parity for Windows Issue Type: New Feature Affects Versions: PUP 5.3.3 Assignee: Unassigned Components: Types and Providers Created: 2018/01/24 11:46 PM Environment: Windows Priority: Normal Reporter: Paul Anderson In Linux, Puppet typically runs as root (full privileges) and can leverage the exec resource's user parameter to run a command as a local user. In Windows, this parity is lacking and it's increasingly causing problems for Puppet users. It would be nice to run things as a local user. This issue is further compounded by common Microsoft System Administration use cases, where various pieces of software are installed and run as domain service accounts. For instance, the SQL Server module does it with some gnarly Ruby in a provider by passing parameters to the installer. I suggest writing a custom installation provider for software requiring a
Jira (PUP-8380) Puppet considers plan with invalid parameter name as valid
Title: Message Title Henrik Lindberg commented on PUP-8380 Re: Puppet considers plan with invalid parameter name as valid I am fine with not allowing leading underscore in parameter names for plans. (The reason it works is because plans are implemented as a kind of Function, and they do allow leading underscore). 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-8394) cache/locales/config.yaml not stable across runs
Title: Message Title Daniel Parks created an issue Puppet / PUP-8394 cache/locales/config.yaml not stable across runs Issue Type: Bug Assignee: Unassigned Created: 2018/01/24 11:35 PM Priority: Normal Reporter: Daniel Parks Puppet Version: 5.3.4 Puppet Server Version: 2018.1.0-rc8 OS Name/Version: various /opt/puppetlabs/puppet/cache/locales/config.yaml often changes despite no code changes being made. It appears to be random. The only changes are the names of the project and package, and that swaps between powershell and mongodb. This has been going on for a while; I think it was present in Hoyt. Desired Behavior: No changes to locales. Actual Behavior: Info: Retrieving locales Debug: Dynamically-bound server lookup failed, falling back to server setting
Jira (PDB-3802) facts-blacklist seemingly only honors blacklisting facts in the middle of the setting array
Title: Message Title Geoff Nichols updated an issue PuppetDB / PDB-3802 facts-blacklist seemingly only honors blacklisting facts in the middle of the setting array Change By: Geoff Nichols Team: Data Platform 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-1811) Amazon Linux v2 os.release.full acceptance test fails - expecting "2.0"
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1811 Amazon Linux v2 os.release.full acceptance test fails - expecting "2.0" Change By: Geoff Nichols Release Notes: Not Needed 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-1812) Bump facter version to 3.6.9
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1812 Bump facter version to 3.6.9 Change By: Geoff Nichols Release Notes: Not Needed 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-8382) Bump puppet version to 4.10.10
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8382 Bump puppet version to 4.10.10 Change By: Geoff Nichols Release Notes: Not Needed 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 Release Notes: Not Needed 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-1788) Facter acceptance test changes needed for el-7-aarch64
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1788 Facter acceptance test changes needed for el-7-aarch64 Change By: Geoff Nichols Release Notes: Not Needed 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-1067) Custom Object Variables support for Nagios
Title: Message Title
Jonno Walmsley commented on PUP-1067
Re: Custom Object Variables support for Nagios
Not sure what the etiquette is on reopening a ticket that was closed this long ago, but I am pretty keen to see this feature implemented. We utilise custom vars in nagios a fair bit, and would really like to manage them via puppet.
Something like this would be ideal:
@@nagios_host { 'foobar':
ensure => present,
address => '1.2.3.4',
...
custom_variables => {
foo => bar,
blue => blah,
},
}
Which would set:
Jira (PUP-8393) Standard Array conversions do not work on return value from tree_each function
Title: Message Title Johnson Earls created an issue Puppet / PUP-8393 Standard Array conversions do not work on return value from tree_each function Issue Type: Bug Affects Versions: PUP 5.3.3 Assignee: Henrik Lindberg Components: Functions Created: 2018/01/24 4:54 PM Priority: Normal Reporter: Johnson Earls I am trying to see what the tree_each function actually produces, to see how I could use it for complex tree transformations. I went with the simplest approach first: # t1.pp
Jira (BOLT-277) SSL default makes winrm harder to use
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-277 SSL default makes winrm harder to use Change By: Michael Smith Sub-team: bolt Bolt 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-277) SSL default makes winrm harder to use
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-277 SSL default makes winrm harder to use Change By: Michelle Fredette Labels: resolved-issue-added 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-277) SSL default makes winrm harder to use
Title: Message Title Michelle Fredette commented on BOLT-277 Re: SSL default makes winrm harder to use added a resolved issue note. 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-268) Investigate using log4r for logging and stdoutoutput in bolt
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-268 Investigate using log4r for logging and stdoutoutput in bolt Change By: Michael Smith Sub-team: bolt Bolt 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-268) Investigate using log4r for logging and stdoutoutput in bolt
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-268 Investigate using log4r for logging and stdoutoutput in bolt Change By: Michael Smith Release Notes: Not Needed 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-213) Bolt plan help includes --nodes
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-213
Bolt plan help includes --nodes
Change By:
Michael Smith
Release Notes Summary:
{{bolt plan --help}} no longer documents --nodes as an option, as it was never a valid option.
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 (BOLT-289) Standardize Target object
Title: Message Title Michelle Fredette commented on BOLT-289 Re: Standardize Target object added release note. 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-289) Standardize Target object
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-289 Standardize Target object Change By: Michelle Fredette Labels: docs_reviewed 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-8363) Do not use system_uptime fact as a source of randomness in acceptance test
Title: Message Title Justin Stoller updated an issue Puppet / PUP-8363 Do not use system_uptime fact as a source of randomness in acceptance test Change By: Justin Stoller Release Notes: Not Needed 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-318) I want to refer to inventory groups as targets
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-318 I want to refer to inventory groups as targets Issue Type: New Feature Assignee: Unassigned Created: 2018/01/24 4:30 PM Priority: Normal Reporter: Alex Dreyer Previous discussion: Where bolt now parses "urls" to resolve targets bolt should first check if the string matches an inventory group. If it does bolt should target all nodes in that group instead of a single target with that hostname. Questions: Where should this happen? Are we ok using the same groups for config values as targetting?(previously yes) Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (BOLT-286) Clean up Bolt::Result ExecutionResult interface
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-286 Clean up Bolt::Result ExecutionResult interface Change By: Michelle Fredette Labels: docs_reviewed 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-104) Support inventory file in bolt
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-104 Support inventory file in bolt Change By: Alex Dreyer Assignee: Alex Dreyer 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-307) Standardize success and failure for plans
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-307 Standardize success and failure for plans Change By: Michael Smith Assignee: Michael Smith 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-1974) Theme: Sensitive Data in Catalogs
Title: Message Title
Eric Delaney commented on PUP-1974
Re: Theme: Sensitive Data in Catalogs
@henrik Sure, I linked a ticket PUP-8136, in the logging system for parameter values, we redact the values by using a "%s" in the format string.
event.message = param.format(_("change from %s to %s failed: "),
This makes it really hard to set this up for translation. We just need to keep translation of strings we are logging in mind so that we don't have to refactor this later.
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-1974) Theme: Sensitive Data in Catalogs
Title: Message Title
Eric Delaney updated an issue
Puppet / PUP-1974
Theme: Sensitive Data in Catalogs
Change By:
Eric Delaney
THIS IS A CROSS TEAM EPIC - DO NOT PUT IN A SPRINT. EACH TEAM NEEDS SEPARATE EPIC SUPPORTING THIS.Sensitive information such as passwords or key files contained within Puppet catalogs leaks into locations such as PuppetDB or syslog. This elevates the necessary security that must be enforced on these external systems.It would be valuable to give manifest/module authors the ability to specify resource properties (such as attributes or titles) which are sensitive. Components downstream from the catalog compiler could then choose how to handle sensitive data. For example, the master could redact such fields from the catalog before sending it to PuppetDB. The agent could be configured to obscure sensitive resource titles from the log when they are acted upon.One possible way to do this would be the addition of a "sensitive" resource type that is compiled into the catalog. Each instance would specific resource fields to be selected and the preferred means of redaction. These changes need to taken I18N support into consideration . The strings we create should use '%{variable}' style formatting to enable i18n string decorations
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,
Jira (BOLT-222) run_* functions should abort on error
Title: Message Title Michelle Fredette commented on BOLT-222 Re: run_* functions should abort on error Added a release note. 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-222) run_* functions should abort on error
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-222 run_* functions should abort on error Change By: Michelle Fredette Labels: docs_reviewed 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-209) Bolt should exit 2 when some nodes fail for commands, scripts, tasks and files
Title: Message Title Michelle Fredette commented on BOLT-209 Re: Bolt should exit 2 when some nodes fail for commands, scripts, tasks and files Add improvement note. 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-209) Bolt should exit 2 when some nodes fail for commands, scripts, tasks and files
Title: Message Title Michelle Fredette updated an issue Puppet Task Runner / BOLT-209 Bolt should exit 2 when some nodes fail for commands, scripts, tasks and files Change By: Michelle Fredette Labels: docs_reviewed 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-317) Handle parsing lists of targets in a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-317 Handle parsing lists of targets in a plan Change By: Alex Dreyer Sprint: Bolt Kanban Discover/Design 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-317) Handle parsing lists of targets in a plan
Title: Message Title Alex Dreyer commented on BOLT-317 Re: Handle parsing lists of targets in a plan Also that would mean we split Array[Target] differently from Array[String] in the CLI. Since everyone else feels strongly about this I'll just kick this ticket back to design and block it on the larger effort to handle parsing structured data from the CLI. 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-317) Handle parsing lists of targets in a plan
Title: Message Title Alex Dreyer commented on BOLT-317 Re: Handle parsing lists of targets in a plan If we weren't doing other parsing magically I think that would make sense. But since we already parse strings and we plan to resolve those strings against inventory it seems reasonable to have a single unified way to convert strings to targets. 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-317) Handle parsing lists of targets in a plan
Title: Message Title Henrik Lindberg commented on BOLT-317 Re: Handle parsing lists of targets in a plan Sound much better (that it is a CLI concern how text on the CLI (a comma separate string list) is turned into an Array of Target). 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-1974) Theme: Sensitive Data in Catalogs
Title: Message Title Henrik Lindberg commented on PUP-1974 Re: Theme: Sensitive Data in Catalogs Eric Delaney You made a note that I18N should be considered when designing this. Can you elaborate on your thoughts? 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-317) Handle parsing lists of targets in a plan
Title: Message Title Michael Smith commented on BOLT-317 Re: Handle parsing lists of targets in a plan Along the line Nick's going, I saw this as: identify a plan has a Target or Array[Target] argument coerce CLI parameters with that type, doing similar transformations as we do for --nodes on the other subcommands. 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-317) Handle parsing lists of targets in a plan
Title: Message Title Nick Lewis commented on BOLT-317 Re: Handle parsing lists of targets in a plan Should the parsing magic be done in bolt instead? We could load the plan and find if some argument expects a Target. Making the comma-separated string just a syntactic sugar for the CLI seems the most intuitive to me. For the case of a plan calling another plan, it should never reasonably be passing a comma-separated string of targets, so I don't think that's so important. 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-317) Handle parsing lists of targets in a plan
Title: Message Title Alex Dreyer commented on BOLT-317 Re: Handle parsing lists of targets in a plan Also I think we should make TargetorTargets a public type in boltlib so plan authors can use it. Is there a reason it was private? 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-8383) /opt/puppetlabs/puppet/cache/facts.d]/mode: mode changed '0755' to '0777'
Title: Message Title Henrik Lindberg commented on PUP-8383 Re: /opt/puppetlabs/puppet/cache/facts.d]/mode: mode changed '0755' to '0777' Are you saying that on a freshly installed puppet without any of your manifest code - that it changes mode on /opt/puppetlabs/puppet/cache/facts.d on an agent that calls in? Or is it changing on the master? Can you elaborate on the steps to reproduce this? 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-8383) /opt/puppetlabs/puppet/cache/facts.d]/mode: mode changed '0755' to '0777'
Title: Message Title Henrik Lindberg assigned an issue to BellaX Puppet / PUP-8383 /opt/puppetlabs/puppet/cache/facts.d]/mode: mode changed '0755' to '0777' Change By: Henrik Lindberg Assignee: BellaX 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-317) Handle parsing lists of targets in a plan
Title: Message Title Alex Dreyer commented on BOLT-317 Re: Handle parsing lists of targets in a plan I agree with parse_targets instead of parse_urls. I had come to that conclusion myself and may go even further to "resolve_targets" to anticipate handling strings that refer to inventory. If the user has to call parse intentionally it just becomes boiler plate at the top of every plan. The core complaint we keep hearing is that plan authors have to call split at the top of their plans. There is already parsing magic in the run_* functions to handle parsing strings we should just make it a little better "targets" is now a single array passed to all run_* functions not a repeated param to enable option passing. This will always behave the same passing the targets param to the "resolve_targets" method that parses any strings it encounters and flattens any sub arrays of Target objects 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-317) Handle parsing lists of targets in a plan
Title: Message Title Thomas Hallgren commented on BOLT-317 Re: Handle parsing lists of targets in a plan The name parse_urls is not ideal for two reasons: a) what's being parsed is a comma separated list and an url may contain commas. b) a Target may well contain a fqdn instead of a url. The name parse_targets is better (and enough I think?). I agree with Henrik Lindberg regarding #2. I consider it bad design to change function behavior depending on the number of arguments. 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-317) Handle parsing lists of targets in a plan
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-317 Handle parsing lists of targets in a plan Change By: Alex Dreyer Assignee: Alex Dreyer 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-287) Standardize calling for run_ functions on nodes.
Title: Message Title Alex Dreyer commented on BOLT-287 Re: Standardize calling for run_ functions on nodes. the first bullet may complicate logging that currently happens in the block passed to yield. 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-317) Handle parsing lists of targets in a plan
Title: Message Title Henrik Lindberg commented on BOLT-317 Re: Handle parsing lists of targets in a plan I think #2 "The run_* functions should use Target.parse_urls if they are given a single string as the Target." is magic and will create a potential source of problems. Better to let the user call the parse function when needed. 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-8392) Back Port PUP-8225 into 4.10.z
Title: Message Title Jennifer Solman created an issue Puppet / PUP-8392 Back Port PUP-8225 into 4.10.z Issue Type: Task Assignee: Unassigned Created: 2018/01/24 2:49 PM Fix Versions: PUP 4.10.z Priority: Normal Reporter: Jennifer Solman The behavior described in PUP-8263 is present in 4.10.x. The relevant code changes were checked into the parent ticket PUP-8225. All of the buggy code from PUP-8225 is present in 4.10.x, but is masked by an additional issue in that code base. Most likely all code from PUP-8225 needs to be back ported together. Add Comment
Jira (PUP-8369) test direct_puppet/supports_utf8.rb is always skipped
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8369 test direct_puppet/supports_utf8.rb is always skipped Change By: Josh Cooper Release Notes: Not Needed 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-5426) config set ignores --section and can insert duplicate settings if they are in [main]
Title: Message Title Josh Cooper commented on PUP-5426 Re: config set ignores --section and can insert duplicate settings if they are in [main] Merged to master in https://github.com/puppetlabs/puppet/commit/31ed4cfda46f5869f4cb978896081a5fc9c54f4e Verified original case works and changes the environment setting in the node_ordering section # This file can be used to override the default puppet settings. # See the following links for more details on what settings are available: # - https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html # - https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html # - https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html # - https://docs.puppetlabs.com/references/latest/configuration.html [main] server = exl7i0vi62ouagu.delivery.puppetlabs.net environment = production
Jira (PDOC-204) document puppetlabs-postgresql with puppet-strings
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-204 document puppetlabs-postgresql with puppet-strings Issue Type: Sub-task Assignee: Unassigned Created: 2018/01/24 2:24 PM Priority: Normal Reporter: Eric Putnam 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 (PDOC-205) document puppetlabs-tagmail with puppet-strings
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-205 document puppetlabs-tagmail with puppet-strings Issue Type: Sub-task Assignee: Unassigned Created: 2018/01/24 2:24 PM Priority: Normal Reporter: Eric Putnam 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 (PDOC-202) document puppetlabs-apache with puppet-strings
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-202 document puppetlabs-apache with puppet-strings Issue Type: Sub-task Assignee: Unassigned Created: 2018/01/24 2:23 PM Priority: Normal Reporter: Eric Putnam 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 (PDOC-200) document puppetlabs-mysql with puppet-strings
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-200 document puppetlabs-mysql with puppet-strings Issue Type: Sub-task Assignee: Unassigned Created: 2018/01/24 2:23 PM Priority: Normal Reporter: Eric Putnam 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 (PDOC-201) document puppetlabs-stdlib with puppet-strings
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-201 document puppetlabs-stdlib with puppet-strings Issue Type: Sub-task Assignee: Unassigned Created: 2018/01/24 2:23 PM Priority: Normal Reporter: Eric Putnam 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 (PDOC-203) document puppetlabs-concat with puppet-strings
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-203 document puppetlabs-concat with puppet-strings Issue Type: Sub-task Assignee: Unassigned Created: 2018/01/24 2:24 PM Priority: Normal Reporter: Eric Putnam 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 (PDOC-199) document puppetlabs-ntp with puppet-strings
Title: Message Title Eric Putnam created an issue Puppet Strings / PDOC-199 document puppetlabs-ntp with puppet-strings Issue Type: Sub-task Assignee: Unassigned Created: 2018/01/24 2:22 PM Priority: Normal Reporter: Eric Putnam 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 (BOLT-289) Standardize Target object
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-289 Standardize Target object Change By: Alex Dreyer Release Notes Summary: *breaking change*The `host` method moved to `uri` 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-289) Standardize Target object
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-289 Standardize Target object Change By: Alex Dreyer Issue Type: Task 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 (BOLT-286) Clean up Bolt::Result ExecutionResult interface
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-286
Clean up Bolt::Result ExecutionResult interface
Change By:
Alex Dreyer
Release Notes Summary:
*breaking change*The `run_command`, `run_script`, `run_task` and `upload_file` functions now return a `ResultSet` object which behaves like an `Array` of `Result` objects rather then a hash of `Variant[Data, Error]` objects. Plans and functions that interacted with `ExecutionResult` will have to be updated to interact with `ResultSet` instead.Examples:```$result.each |$name, $result| {}becomes $result.each |$result| { $name = $result.target.name}$result['node.example.com'] becomes$result.find('node.example.com')run_task(, $result.ok_nodes, )becomesrun_task(, $result.ok_set.targets ...)```
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-317) Handle parsing lists of targets in a plan
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-317 Handle parsing lists of targets in a plan Change By: Michael Smith Sub-team: Bolt Team: Direct Change 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-286) Clean up Bolt::Result ExecutionResult interface
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-286 Clean up Bolt::Result ExecutionResult interface Change By: Alex Dreyer Issue Type: Task 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 (BOLT-277) SSL default makes winrm harder to use
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-277 SSL default makes winrm harder to use Change By: Alex Dreyer Release Notes Summary: improved logging for winrm connections failures 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-222) run_* functions should abort on error
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-222 run_* functions should abort on error Change By: Alex Dreyer Release Notes Summary: *breaking change*the run functions in bolt plans will now raise an exception if they fail on any nodes. To catch these and return the resultset pass the `'_catch_errors' => true` option at the end of run function call. 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-209) Bolt should exit 2 when some nodes fail for commands, scripts, tasks and files
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-209 Bolt should exit 2 when some nodes fail for commands, scripts, tasks and files Change By: Alex Dreyer Release Notes Summary: Bolt will now exit 2 when `run command`, `run script`, `run task`, or `file upload` fails on some nodes. 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-222) run_* functions should abort on error
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-222 run_* functions should abort on error Change By: Alex Dreyer Issue Type: Story 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-8381) modifycmd does not correctly catch and handle the `password_warn_days` option
Title: Message Title
Eric Delaney commented on PUP-8381
Re: modifycmd does not correctly catch and handle the `password_warn_days` option
My code change works for creating the user or recreating the user from the output from 'puppet resource user username' which didn't work before.
[root@sw9l57yakr77vl2 ~]# puppet resource user testy > testy_complete.pp
[root@sw9l57yakr77vl2 ~]# cat testy_complete.pp
user { 'testy':
ensure => 'present',
gid=> 65534,
home => '/home/testy',
password => '!!',
password_max_age => 123456,
password_min_age => 1,
password_warn_days => 987,
Jira (PUP-8381) modifycmd does not correctly catch and handle the `password_warn_days` option
Title: Message Title
Eric Delaney commented on PUP-8381
Re: modifycmd does not correctly catch and handle the `password_warn_days` option
I pulled the latest master and the setting of password_warn_days does not work:
[root@hbrpl0yhyjgk9pj ~]# cat user.pp
user { 'testy':
ensure => 'present',
comment=> 'test user',
gid=> 996,
home => '/tmp',
password => '!!',
shell => '/sbin/nologin',
uid=> 1234,
}
Jira (PUP-8369) test direct_puppet/supports_utf8.rb is always skipped
Title: Message Title Josh Cooper commented on PUP-8369 Re: test direct_puppet/supports_utf8.rb is always skipped Merged to 4.10.x in https://github.com/puppetlabs/puppet/commit/0ad8562583162e78003e5369f6a5b936ac422fd9 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-317) Handle parsing lists of targets in a plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-317 Handle parsing lists of targets in a plan Change By: Alex Dreyer Currently if a plan is going to take a list of targets it has to do so on it's own.1. We should create a puppet function parse_targets that takes a string and returns and array of Targets from that Target.parse_urls2. We should fix Target.parse_urls so it splits on any white space. This probably caused a regression in passing files to --node3. The run_* functions should use Target.parse_urls if they are given a single string as the Target. 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-317) Handle parsing lists of targets in a plan
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-317 Handle parsing lists of targets in a plan Issue Type: New Feature Assignee: Unassigned Created: 2018/01/24 1:33 PM Priority: Normal Reporter: Alex Dreyer Currently if a plan is going to take a list of targets it has to do so on it's own. 1. We should create a puppet function parse_targets that takes a string and returns and array of Targets from that Target.parse_urls 2. We should fix Target.parse_urls so it splits on any white space. This probably caused a regression in passing files to --node 3. The run_* functions should use Target.parse_urls if they are given a single string as the Target. Add Comment
Jira (PUP-8337) Package source on Windows errors out on deduped installation files
Title: Message Title Kenn Hussey commented on PUP-8337 Re: Package source on Windows errors out on deduped installation files Ethan Brown please add release notes for this issue, if needed. Thanks! 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-8361) Create a CI job to generate manpages
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8361 Create a CI job to generate manpages Change By: Josh Cooper Fix Version/s: PUP 4.10.11 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-8361) Create a CI job to generate manpages
Title: Message Title Josh Cooper commented on PUP-8361 Re: Create a CI job to generate manpages Merged to 4.10.x in https://github.com/puppetlabs/puppet/commit/2f54311b6aaafbc1d14b4ed9f2c37bc2e7da0c17 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-8363) Do not use system_uptime fact as a source of randomness in acceptance test
Title: Message Title Kenn Hussey commented on PUP-8363 Re: Do not use system_uptime fact as a source of randomness in acceptance test Justin Stoller please add release notes for this issue, if needed. Thanks! 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-1916) puppet cert clean cannot remove signing requests
Title: Message Title Nick Walker updated an issue Puppet / PUP-1916 puppet cert clean cannot remove signing requests Change By: Nick Walker CS Priority: Needs Priority 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-8368) Non-English windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8368 Non-English windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server Change By: Kenn Hussey Flagged: Impediment 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-1597) "Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug." on AIX
Title: Message Title Jeremiah Powell updated an issue Facter / FACT-1597 "Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug." on AIX Change By: Jeremiah Powell Attachment: facter_trace_20180124.txt 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-1797) Amazon EC2 C5 Instances not detected as is_virtual causing ec2_metadata fact data not to resolve
Title: Message Title Branan Riley updated an issue Facter / FACT-1797 Amazon EC2 C5 Instances not detected as is_virtual causing ec2_metadata fact data not to resolve Change By: Branan Riley Sprint: Platform OS Grooming/Triage 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 (FACT-1797) Amazon EC2 C5 Instances not detected as is_virtual causing ec2_metadata fact data not to resolve
Title: Message Title Casey Williams assigned an issue to Casey Williams Facter / FACT-1797 Amazon EC2 C5 Instances not detected as is_virtual causing ec2_metadata fact data not to resolve Change By: Casey Williams Assignee: Casey Williams 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-8368) Non-English windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server
Title: Message Title Josh Cooper commented on PUP-8368 Re: Non-English windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server Ruby patch merged to puppet-agent#5.3.x in https://github.com/puppetlabs/puppet-agent/commit/60b81cf1a46c43426ce1dbf0537cc0b02a7323f6 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-8368) Non-English windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server
Title: Message Title Eric Delaney commented on PUP-8368 Re: Non-English windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server Re-enable windows test Merged to 5.3.x at https://github.com/puppetlabs/puppet/commit/dba8e0fbc50d9822843a847303019a6e40c5de61 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-8368) Non-English windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8368 Non-English windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server Change By: Josh Cooper Summary: Japanese Non-English windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server 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-8368) Japanese windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8368 Japanese windows puppet agent run fails with 'incompatible character encodings' when run against non-existent server Change By: Josh Cooper Release Notes Summary: Puppet agents on non-English Windows hosts would crash if they encountered a socket error, such as failing to connect to the default server named "puppet". 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-8386) Prepare JIRA for release (Puppet Platform 5.3.4)
Title: Message Title Kenn Hussey commented on PUP-8386 Re: Prepare JIRA for release (Puppet Platform 5.3.4) Fixed in puppet-agent 5.3.4 https://tickets.puppetlabs.com/issues/?filter=30935 Introduced in puppet-agent 5.3.4 https://tickets.puppetlabs.com/issues/?filter=30936 Fixed in Puppet Platform 5.3.4 https://tickets.puppetlabs.com/issues/?filter=30937 Introduced in Puppet Platform 5.3.4 https://tickets.puppetlabs.com/issues/?filter=30938 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-307) Standardize success and failure for plans
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-307
Standardize success and failure for plans
Change By:
Michael Smith
Plan success should be defined as "returning" any value.Plan failure should be defined as "raising" an Error.h3. raise_error function:(moved to BOLT-123)h3. catch_errors option:Add a new {{\_catch\_errors}} option on the {{run_plan}} function. By default plan execution should stop if a plan called with run_plan errors. When a plan is called with {{\_catch\_errors => true}} it should instead return a pcore {{Error}} object containing the error. This should work both for the exceptions thrown by run_* and from the raise_error function. This should will not catch errors that cannot be obviously converted to other types of failure (such as the {{ Error fail }} datatype because they don't have a kind/msg/details function). h3. output:The plan outputter should display error message in red for {{human}} format and the entire error hash as pretty printed json for the {{json}} format before exiting. h3. Questions:1. Is it a problem that _catch_error in a plan returns an error object while catch_error in a task/command/file/script returns a ResultSet?2. How do we interact with the Error Datatype?
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
Jira (BOLT-307) Standardize success and failure for plans
Title: Message Title
Michael Smith commented on BOLT-307
Re: Standardize success and failure for plans
We opted for _catch_errors as a boolean initially to make it easy to remember how to use, and can expand it to a boolean/enum variant later if needed.
The Error type seems pretty usable, since that's essentially what we're modeling raise_error on (has a message, kind, details). While we've introduced ok? as a pattern for interrogating ResultSets, that doesn't generalize to other types, so we don't gain much from providing an Error type that responds to ok?.
Interrogating results based on type seems like a somewhat common pattern in puppet via the case statement, i.e.
case $result {
Error: {
"Received an error[${$result.kind}]: ${$result.message}"
}
default: {
"Everything's fine, we're all fine here"
}
}
Jira (PDB-3819) Manually smoke test all artifacts (PuppetDB 5.1.4)
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3819 Manually smoke test all artifacts (PuppetDB 5.1.4) Change By: Kenn Hussey Summary: Manually smoke test all artifacts ( Puppet Platform PuppetDB 5. 3 1 .4) 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-3820) Destroy release branches, pipelines, and update winston (PuppetDB 5.1.4)
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3820 Destroy release branches, pipelines, and update winston (PuppetDB 5.1.4) Change By: Kenn Hussey Summary: Destroy release branches, pipelines, and update winston ( Puppet Platform PuppetDB 5. 3 1 .4) 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-3816) Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.1.4)
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3816 Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.1.4) Change By: Kenn Hussey Summary: Reconcile git commits, JIRA tickets, and versions ( Puppet Platform PuppetDB 5. 3 1 .4) 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-3818) Tag and build artifacts (PuppetDB 5.1.4)
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3818 Tag and build artifacts (PuppetDB 5.1.4) Change By: Kenn Hussey Summary: Tag and build artifacts ( Puppet Platform PuppetDB 5. 3 1 .4) 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-3817) Merge-up, branch, and create pipelines (PuppetDB 5.1.4)
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3817 Merge-up, branch, and create pipelines (PuppetDB 5.1.4) Change By: Kenn Hussey Summary: Merge-up, branch, and create pipelines ( Puppet Platform PuppetDB 5. 3 1 .4) 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-3817) Merge-up, branch, and create pipelines (Puppet Platform 5.3.4)
Title: Message Title Molly Waggett assigned an issue to Russell Mull PuppetDB / PDB-3817 Merge-up, branch, and create pipelines (Puppet Platform 5.3.4) Change By: Molly Waggett Assignee: russ Russell Mull 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-3818) Tag and build artifacts (Puppet Platform 5.3.4)
Title: Message Title Molly Waggett assigned an issue to Russell Mull PuppetDB / PDB-3818 Tag and build artifacts (Puppet Platform 5.3.4) Change By: Molly Waggett Assignee: russ Russell Mull 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-3819) Manually smoke test all artifacts (Puppet Platform 5.3.4)
Title: Message Title Molly Waggett assigned an issue to Russell Mull PuppetDB / PDB-3819 Manually smoke test all artifacts (Puppet Platform 5.3.4) Change By: Molly Waggett Assignee: russ Russell Mull 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-3820) Destroy release branches, pipelines, and update winston (Puppet Platform 5.3.4)
Title: Message Title Molly Waggett assigned an issue to Russell Mull PuppetDB / PDB-3820 Destroy release branches, pipelines, and update winston (Puppet Platform 5.3.4) Change By: Molly Waggett Assignee: russ Russell Mull 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-3816) Reconcile git commits, JIRA tickets, and versions (Puppet Platform 5.3.4)
Title: Message Title Molly Waggett assigned an issue to Russell Mull PuppetDB / PDB-3816 Reconcile git commits, JIRA tickets, and versions (Puppet Platform 5.3.4) Change By: Molly Waggett Assignee: russ Russell Mull 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-3816) Reconcile git commits, JIRA tickets, and versions (Puppet Platform 5.3.4)
Title: Message Title Molly Waggett created an issue PuppetDB / PDB-3816 Reconcile git commits, JIRA tickets, and versions (Puppet Platform 5.3.4) Issue Type: Task Assignee: russ Created: 2018/01/24 10:48 AM Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2018-01-31) Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PDB-3818) Tag and build artifacts (Puppet Platform 5.3.4)
Title: Message Title Molly Waggett created an issue PuppetDB / PDB-3818 Tag and build artifacts (Puppet Platform 5.3.4) Issue Type: Task Assignee: russ Created: 2018/01/24 10:48 AM Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2018-01-31) Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PDB-3819) Manually smoke test all artifacts (Puppet Platform 5.3.4)
Title: Message Title Molly Waggett created an issue PuppetDB / PDB-3819 Manually smoke test all artifacts (Puppet Platform 5.3.4) Issue Type: Task Assignee: russ Created: 2018/01/24 10:48 AM Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2018-01-31) Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Jira (PDB-3820) Destroy release branches, pipelines, and update winston (Puppet Platform 5.3.4)
Title: Message Title Molly Waggett created an issue PuppetDB / PDB-3820 Destroy release branches, pipelines, and update winston (Puppet Platform 5.3.4) Issue Type: Task Assignee: russ Created: 2018/01/24 10:48 AM Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2018-01-31) Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
