Jira (PUP-8528) Remove WriteOnlyYaml node terminus
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8528 Remove WriteOnlyYaml node terminus Change By: Josh Cooper Acceptance Criteria: It should no longer be possible to set the node terminus to write_only_yaml. During a catalog compilation, puppetserver should never write the node's data to /opt/puppetlabs/server/data/... 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-8446) Remove "puppet man" face application
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8446 Remove "puppet man" face application Change By: Josh Cooper Release Notes Summary: The puppet-agent package installs man pages, so `man puppet` will produce useful results. Puppet's help system is also available, e.g. `puppet help`. The `puppet man` application is no longer needed and has been removed. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8988) Don't pluginsync vendored modules
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8988 Don't pluginsync vendored modules Change By: Josh Cooper Team: 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 (PUP-8819) Create the CI pipeline
Title: Message Title Josh Cooper commented on PUP-8819 Re: Create the CI pipeline PR https://github.com/puppetlabs/ci-job-configs/pull/4720 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-8823) Move all outstanding PUP tickets to Modules
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8823 Move all outstanding PUP tickets to Modules 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-8822) Remove type/provider code from puppet
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8822 Remove type/provider code from puppet 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-8820) Release 1.0.0 to the forge
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8820 Release 1.0.0 to the forge 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-8821) Package module into puppet-agent
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8821 Package module into puppet-agent 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-8819) Create the CI pipeline
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8819 Create the CI pipeline 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-8818) Extract the code & verify the module
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8818 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-8721) Agent Functions - Set up Vault Server internally for testing
Title: Message Title Tony Vu commented on PUP-8721 Re: Agent Functions - Set up Vault Server internally for testing Initially, we are going to go with a docker-compose setup with Vault and Puppetserver for initial development; as we get closer to needing tests in CI, we will revisit this and see the best way to get the same setup with a beaker acceptance test. 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-8721) Agent Functions - Set up Vault Server internally for testing
Title: Message Title Tony Vu assigned an issue to Tony Vu Puppet / PUP-8721 Agent Functions - Set up Vault Server internally for testing Change By: Tony Vu Assignee: Tony Vu 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-8723) Agent Functions - Create Vault deferred evaluation
Title: Message Title Tony Vu assigned an issue to Tony Vu Puppet / PUP-8723 Agent Functions - Create Vault deferred evaluation Change By: Tony Vu Assignee: Tony Vu 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-8723) Agent Functions - Create Vault deferred evaluation
Title: Message Title Tony Vu assigned an issue to Patrick Carlisle Puppet / PUP-8723 Agent Functions - Create Vault deferred evaluation Change By: Tony Vu Assignee: Tony Vu Patrick Carlisle 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-8939) Administrators are not able to run puppet agent when installed as SYSTEM in some cases
Title: Message Title Erick Banks updated an issue Puppet / PUP-8939 Administrators are not able to run puppet agent when installed as SYSTEM in some cases Change By: Erick Banks Sprint: Windows 2018-07-18 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-684) Apply results aren't directly usable
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-684 Apply results aren't directly usable 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 (BOLT-631) Bolt should support hiera configuration and use it when compiling catalogs
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-631 Bolt should support hiera configuration and use it when compiling catalogs Change By: Cas Donoghue Assignee: Cas Donoghue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-684) Apply results aren't directly usable
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-684 Apply results aren't directly usable Change By: Michael Smith Affects Version/s: BOLT 0.21.2 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-684) Apply results aren't directly usable
Title: Message Title
Michael Smith created an issue
Puppet Task Runner / BOLT-684
Apply results aren't directly usable
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/07/10 3:31 PM
Priority:
Normal
Reporter:
Michael Smith
An example plan such as the following errors trying to use what should be Result objects
plan foo::simple (TargetSpec $nodes) {
$results = apply($nodes) {
notify { "hello ${trusted}": }
}
return $results.map |$r| {
$r['logs'].map |$l| { $l['message'] }
Jira (BOLT-684) Apply results aren't directly usable
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-684 Apply results aren't directly usable 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 (PUP-8957) [Regression] PUP-8167 behaviour noted in Puppet AiO 5.5.3
Title: Message Title Branan Riley updated an issue Puppet / PUP-8957 [Regression] PUP-8167 behaviour noted in Puppet AiO 5.5.3 Change By: Branan Riley Labels: service solaris solaris-parity type_and_provider 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 Branan Riley commented on PUP-8957 Re: [Regression] PUP-8167 behaviour noted in Puppet AiO 5.5.3 From memory, and from what I can piece together from the ticket and commit history: The change from returning ensure => stopped to ensure => absent was initially landed in 4.X, and reverted later in the 4.10 series when we determined it was causing regressions That change was intentionally left in the 5.X series, but presumably not well-shaken-out by users since we don't ship FOSS Solaris packages, and our Solaris commercial customers aren't the fastest to upgrade Possibly, some other changes related to improving the behavior of ensure => absent were reverted in 4.10, but NOT left in 5, which has led to the apparent regression of 8167. This is unclear to me - the git history is /super/ gnarly. Anyway, there are a few of options here: Leave the ensure=>absent behavior, and fix the service type to understand what the solaris provider is doing, and thus calling "absent" and "stopped" in sync. This would let us return "absent" from other providers. Revert the "absent" behavior again, and just return "stopped", even though it's wrong Revert all the way back to when trying to mange a nonexistent service would just raise an error, and tell users to stop trying to manage things that don't exist. (we probably shouldn't do this) Make the Solaris provider implement "enablable" fully, so that missing services show as stopped, but trying to enable or start a missing service will still return an error. I think the lasts one is probably best. This means returning "stopped=true,enabled=false" for nonexistent services. This matches the behavior of the systemd provider, and thus most modern Linux systems. Add Comment
Jira (BOLT-647) Support _noop for apply statements
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-647 Support _noop for apply statements 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 (BOLT-647) Support _noop for apply statements
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-647 Support _noop for apply statements 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 (BOLT-675) Integration testing of correct precedence
Title: Message Title Michael Smith assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-675 Integration testing of correct precedence Change By: Michael Smith Assignee: Michael Smith Lucy Wyman 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 Scott McClellan assigned an issue to Branan Riley Puppet / PUP-8957 [Regression] PUP-8167 behaviour noted in Puppet AiO 5.5.3 Change By: Scott McClellan Assignee: Branan Riley 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-683) Make executable configurable
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-683 Make executable configurable Issue Type: Story Assignee: Unassigned Created: 2018/07/10 2:15 PM Priority: Normal Reporter: Michael Smith If Ruby is installed on a Windows system and included in Path, Bolt Apply will attempt to use the installed Ruby interpreter rather than the Ruby included with Puppet Agent, likely resulting in failure. We should make it possible to configure how apply_catalog.rb is invoked over WinRM. Questions How should we implement this? General ability to prepend things to PATH, or specific mapping of extension to executable? Should we special-case this for apply, or make it a general fix? Currently it will have a similar impact on other modules that expect tasks to be applied in a Puppet-aware Ruby, such as package/service/etc. Add Comment
Jira (BOLT-635) Refactor the executor to parallelize multi-target applies
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-635 Refactor the executor to parallelize multi-target applies 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 (BOLT-682) Have nice error message if user tries 'apply' with no PA
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-682 Have nice error message if user tries 'apply' with no PA Issue Type: Task Assignee: Unassigned Created: 2018/07/10 2:06 PM Priority: Normal Reporter: Lucy Wyman We should have a nice error message if a user tries to use the apply keyword and doesn't have puppet agent installed. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-634) Integration tests for apply functionality
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-634 Integration tests for apply functionality Change By: Michael Smith 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-8817) Create the github repo
Title: Message Title Josh Cooper commented on PUP-8817 Re: Create the github repo Done 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-8818) Extract the code & verify the module
Title: Message Title Josh Cooper commented on PUP-8818 Re: Extract the code & verify the module PR https://github.com/puppetlabs/puppetlabs-host_core/pull/1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-675) Integration testing of correct precedence
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-675 Integration testing of correct precedence 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 (PUP-8788) Move all outstanding PUP tickets to Modules
Title: Message Title Josh Cooper commented on PUP-8788 Re: Move all outstanding PUP tickets to Modules Done: https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20MODULES%20AND%20component%20in%20(yumrepo_core)%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC 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-8685) Migrate gemspec info in project_data.yaml to the .gemspec file
Title: Message Title Enis Inan commented on PUP-8685 Re: Migrate gemspec info in project_data.yaml to the .gemspec file This ticket's blocked on figuring out how we ultimately want to build the gem. Do we want to use the existing tooling, and hence ext/project_data.yaml, to create our gem as it is currently done? Or do we want to make the .gemspec itself buildable, taking out all gem-specific stuff from ext/project_data.yaml? The trade-off for the latter is that we will have to declare the gem deps. dynamically, which will not properly show up on the rubygems interface for listing gem dependencies. Or do we want to move towards shipping a single gem instead? Lots of questions. 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-8685) Migrate gemspec info in project_data.yaml to the .gemspec file
Title: Message Title Enis Inan assigned an issue to Branan Riley Puppet / PUP-8685 Migrate gemspec info in project_data.yaml to the .gemspec file Change By: Enis Inan Assignee: Enis Inan Branan Riley 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-1865) Amazon Linux 2 is reported as 4
Title: Message Title Casey Williams updated an issue Facter / FACT-1865 Amazon Linux 2 is reported as 4 Change By: Casey Williams Release Notes Summary: Updates facter to correctly read the format of /etc/system-release under Amazon Linux 2. This corrects the os release fact, which previously fell back to the kernel version. 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 Release Notes Summary: Facter no longer tries to read kstat entries that it does not need to process. This avoids potential permissions issues when run in a zone or as non-root on Solaris. 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-1865) Amazon Linux 2 is reported as 4
Title: Message Title Casey Williams updated an issue Facter / FACT-1865 Amazon Linux 2 is reported as 4 Change By: Casey Williams 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 (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 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 (FACT-1865) Amazon Linux 2 is reported as 4
Title: Message Title Kenn Hussey commented on FACT-1865 Re: Amazon Linux 2 is reported as 4 Casey Williams please add release notes for this issue, if needed. Thanks! 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 Kenn Hussey commented on FACT-1832 Re: Facter Fails on Solaris 11.3 Patch 29.0.4.0 Native Zone. Casey Williams please add release notes for this issue, if needed. Thanks! 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-1869) Make react-components a peer dependency of insights-editor
Title: Message Title Geoff Woodburn updated an issue Facter / FACT-1869 Make react-components a peer dependency of insights-editor Change By: Geoff Woodburn Team: Insights Sprint: Sprint 2018-07-09 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-1869) Make react-components a peer dependency of insights-editor
Title: Message Title Geoff Woodburn created an issue Facter / FACT-1869 Make react-components a peer dependency of insights-editor Issue Type: Task Assignee: Unassigned Created: 2018/07/10 1:17 PM Priority: Normal Reporter: Geoff Woodburn Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (BOLT-681) Manifest block compile will autoload Puppet gem over vendored Puppet
Title: Message Title Michael Smith commented on BOLT-681 Re: Manifest block compile will autoload Puppet gem over vendored Puppet For now this will have to remain as a known issue. I can't think of any good ways to change the autoloading behavior - maybe monkey-loading. Most users should use packaged Bolt, and if they avoid loading Puppet into as well then they won't encounter this problem. 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-681) Manifest block compile will autoload Puppet gem over vendored Puppet
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-681 Manifest block compile will autoload Puppet gem over vendored Puppet Issue Type: Bug Assignee: Unassigned Created: 2018/07/10 1:13 PM Priority: Normal Reporter: Michael Smith With both Puppet and Bolt present as gems, during the manifest block compile Puppet will autoload types starting with gem lib directories. If the Puppet version installed significantly differs from the vendored Puppet version (as in Puppet 5 vs Puppet 6) you can end up with errors like Evaluation Error: Error while evaluating a Resource Statement, Could not autoload puppet/type/file: uninitialized constant Puppet::Util::MethodHelper (file: /home/fred/.puppetlabs/etc/code/modules/foo/plans/simple.pp, line: 12, column: 7) (Puppet::PreformattedError)\n\tfrom /var/lib/gems/2.3.0/gems/bolt-0.21.2/vendored/puppet/lib/puppet/util/classgen.rb:130:in `class_eval'\n
Jira (PUP-8726) Agent Functions - Content negotiation of rich data types to old/new agents
Title: Message Title Henrik Lindberg commented on PUP-8726 Re: Agent Functions - Content negotiation of rich data types to old/new agents With my branch/PR it is possible to load all data types that are in Puppet. The data types in modules will not be present on the agent until we fix plugin sync to include those types. Must also fix loading data types and functions from modules for the feature to be complete. It is very much usable without those though. Regarding rich-data; I expect that to be on by default in newer agents and (naturally) off in existing. If we change "serialize as string" when rich data is written when rich-data is off then we break API since this is how it has worked earlier (and may be expected behaviour by users). However, if content type is negotiated and it says "no rich data please" then it should error IMO. Question is if it is ok to error for older agents (small risk people rely on "to_s" being called on all objects). 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-634) Integration tests for apply functionality
Title: Message Title Michael Smith assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-634 Integration tests for apply functionality Change By: Michael Smith Assignee: Michael Smith Cas Donoghue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-679) Automate updating the version and sha of brew package
Title: Message Title Michael Smith commented on BOLT-679 Re: Automate updating the version and sha of brew package Sure, would be nice to get there eventually. 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-679) Automate updating the version and sha of brew package
Title: Message Title Lucy Wyman commented on BOLT-679 Re: Automate updating the version and sha of brew package Sounds good – should I change this to adding it to jenkins? I mostly thought I had already made this ticket, and didn't see 618 when I filtered for CI Improvements this morning 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-634) Integration tests for apply functionality
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-634 Integration tests for apply functionality Change By: Michael Smith Assignee: Cas Donoghue 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-618) Automate updating homebrew-puppet with Bolt releases
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-618 Automate updating homebrew-puppet with Bolt releases Change By: Michael Smith After release packages are released, we want to push an update to https://github.com/puppetlabs/homebrew-puppet/blob/master/Casks/puppet-bolt.rb with the new version and SHAs.The SHAs need to be calculated after packages have been signed. So there are two options for how we do this- Run Add a job that periodically checks for new package versions at https: rake task in puppetlabs / /downloads.puppet.com/mac, and updates packaging to update homebrew-puppet if new versions are found for the latest released packages . - Add a step in Modify the release process Winston step to include running that updates homebrew-puppet rake 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 s
Jira (BOLT-679) Automate updating the version and sha of brew package
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-679 Automate updating the version and sha of brew package 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-679) Automate updating the version and sha of brew package
Title: Message Title Michael Smith commented on BOLT-679 Re: Automate updating the version and sha of brew package As noted in BOLT-618, making this an automated part of the jenkins release pipeline will have to wait until we can sign packages as part of that pipeline. As a first step BOLT-618 proposes adding a rake task to update homebrew-puppet based on the latest released packages. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-633) Configure modulepath for bolt_catalog
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-633 Configure modulepath for bolt_catalog 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 assigned an issue to Casey Williams Facter / FACT-1832 Facter Fails on Solaris 11.3 Patch 29.0.4.0 Native Zone. Change By: Branan Riley Assignee: Branan Riley Casey Williams 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-1868) Make react-components a proper peer dependency of insights-embed
Title: Message Title Geoff Woodburn created an issue Facter / FACT-1868 Make react-components a proper peer dependency of insights-embed Issue Type: Task Assignee: Geoff Woodburn Created: 2018/07/10 11:26 AM Priority: Normal Reporter: Geoff Woodburn 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 thi
Jira (PUP-8975) Agent Functions - Spike: determine if Deferred type should be implemented w/o Rich Data
Title: Message Title Eric Thompson commented on PUP-8975 Re: Agent Functions - Spike: determine if Deferred type should be implemented w/o Rich Data doing this in the "old" catalog format also probably has issues similar to when Sensitive[t] was implemented. just guessing, but at that time we needed a separate attribute of the list of Senstive attributes. this also wasn't easily handled by puppetdb. also has issues with exported resources, and --show-diff. etc etc etc. we can re-open this if we find more risks with enabling rich data. closing for now 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-8975) Agent Functions - Spike: determine if Deferred type should be implemented w/o Rich Data
Title: Message Title Eric Thompson updated an issue Puppet / PUP-8975 Agent Functions - Spike: determine if Deferred type should be implemented w/o Rich Data Change By: Eric Thompson Summary: Agent Functions - Spike: determine if Deferred type can should be implemented w/o Rich Data 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-8442) type parameters do not honor when default is set to false
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8442 type parameters do not honor when default is set to false Change By: Josh Cooper Sprint: Platform Core 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 (PUP-8967) Use status endpoint to determine if puppetserver is reachable
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8967 Use status endpoint to determine if puppetserver is reachable Change By: Josh Cooper Sprint: Platform Core 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 (PUP-8683) Change http_read_timeout and runtimeout defaults to be less than infinite
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8683 Change http_read_timeout and runtimeout defaults to be less than infinite Change By: Josh Cooper Sprint: Platform Core 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 (PUP-7931) Support HTTPS Compression on report upload
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7931 Support HTTPS Compression on report upload Change By: Josh Cooper Sprint: Platform Core 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 (PUP-7931) Support HTTPS Compression on report upload
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7931 Support HTTPS Compression on report upload Change By: Josh Cooper Sprint: Platform Core Hopper 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 (PUP-8726) Agent Functions - Content negotiation of rich data types to old/new agents
Title: Message Title Eric Thompson commented on PUP-8726 Re: Agent Functions - Content negotiation of rich data types to old/new agents Henrik Lindberg Josh Cooper what more needs to be done to resolve this? an Error when an agent connects which cannot accept rich data seems like the way to go to me. this ticket is ensuring agent/master catalog and content negotiation. do we need something similar with puppetdb? e.g.: exported "rich" resources, queries of rich data, "rich" serialized catalog storage. 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-8918) Separate CA and SSL dirs
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8918 Separate CA and SSL dirs Change By: Maggie Dreyer Epic Status: To Do In Progress 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-680) Simplify scaffolding for powershell tasks with metadata
Title: Message Title Michael Smith commented on BOLT-680 Re: Simplify scaffolding for powershell tasks with metadata I'm not currently in favor of this change: it would require a change to the task specification, that affects how tasks use _noop in existing PE releases we'd want to name it something like _meta anyway to avoid collisions with valid user parameter names I'm not convinced it's that much of an improvement when they still need to go lookup what the metaparameter syntax is to be able to scaffold it, which means it doesn't feel worth the effort I'm open to more input that it would be useful however. 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-680) Simplify scaffolding for powershell tasks with metadata
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-680 Simplify scaffolding for powershell tasks with metadata Change By: Michael Smith Issue Type: Story Improvement 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-680) Simplify scaffolding for powershell tasks with metadata
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-680 Simplify scaffolding for powershell tasks with metadata Issue Type: Story Assignee: Unassigned Created: 2018/07/10 10:40 AM Priority: Normal Reporter: Michael Smith Ethan Brown suggested in https://github.com/puppetlabs/bolt/pull/497#discussion_r199299011 that we simplify creating templates for powershell tasks with PDK by putting metadata under a single hash parameter. Then all powershell tasks could include param( [Parameter(Mandatory = $False)] [Hash] $_meta )
Jira (BOLT-632) Scope for bolt_compile should be set up
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-632 Scope for bolt_compile should be set up 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 (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? merged to puppet#5.5.x in https://github.com/puppetlabs/puppet/commit/23848f32d733c65418bad38f39d612a0968915c1 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-654) Bolt transport api should support SSL
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-654 Bolt transport api should support SSL Change By: Michael Smith The bolt transport api should run over ssl by default. The client should accept an ssl certificate (content not filepath) with the `--cert` flag on startup and use the cert to authenticate future requests from the client. The certificate should be passed directly to the sinatra server and stored in memory as a variable there. Security-wise, we need to either accept only localhost, or have full SSL configuration (ca cert, cert, private key). Questions: - For now should we require that a cert be specified to run? 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.
Jira (PDB-3268) Don't just return nothing from applied-migrations if the query fails
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-3268 Don't just return nothing from applied-migrations if the query fails Change By: Austin Blatt Assignee: Austin Blatt 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-653) Bolt transport api should be configurable
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-653
Bolt transport api should be configurable
Change By:
Michael Smith
There isn't currently a way to configure the bolt transport api each time it's run from the caller. The bolt- transport-api server should read it's HOCON config and from {{/etc/puppetlabs/bolt-server/conf . d/*.conf}}. To verify this works the first option to pass in should be "port", to configure the port the transport api should run on. Load and merge all conf files in conf.d. {code}webserver: { port: 1234}{code}
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 opt
Jira (BOLT-679) Automate updating the version and sha of brew package
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-679 Automate updating the version and sha of brew package Issue Type: Task Assignee: Unassigned Created: 2018/07/10 9:46 AM Priority: Normal Reporter: Lucy Wyman We should: automate https://github.com/puppetlabs/winston/blob/master/files/bolt/release_ticket_descriptions.yaml#L21 Remove the ticket creation from winston Add the automation to the jenkins pipeline Add Comment
Jira (BOLT-653) Bolt transport api should be configurable
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-653 Bolt transport api should be configurable Change By: Lucy Wyman There isn't currently a way to configure the bolt transport api each time it's run from the caller. The bolt-transport-api should read it's config and . To verify this works the first option to pass in should be "port", to configure the port the transport api should run on. Questions: - Where should the config live? 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-565) Apply from Plans
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-565 Apply from Plans Change By: Lucy Wyman Epic Colour: ghx-label- 1 2 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-634) Integration tests for apply functionality
Title: Message Title Michael Smith assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-634 Integration tests for apply functionality Change By: Michael Smith 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-8606) Module-defined data types are very verbose when displayed
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8606 Module-defined data types are very verbose when displayed Change By: Kenn Hussey Flagged: Impediment 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-8615) sort_formats does not sort consistently with MRI Ruby which causes issues when find .find processes the hash to select a choice
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-8615 sort_formats does not sort consistently with MRI Ruby which causes issues when find .find processes the hash to select a choice Change By: Kenn Hussey Flagged: Impediment 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 Fix Version/s: PUP 5.5.z Fix Version/s: PUP 5.5.4 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-3961) Check builds, promote to PE (PuppetDB 5.2.3)
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3961 Check builds, promote to PE (PuppetDB 5.2.3) Change By: Kenn Hussey Due Date: 2018/07/ 14 13 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-3958) Merge-up, branch, and create pipelines (PuppetDB 5.2.3)
Title: Message Title
Kenn Hussey created an issue
PuppetDB / PDB-3958
Merge-up, branch, and create pipelines (PuppetDB 5.2.3)
Issue Type:
Task
Assignee:
Zachary Kent
Created:
2018/07/10 7:59 AM
Due Date:
2018/07/10
Priority:
Normal
Reporter:
Kenn Hussey
(Initial planned release date: 2018-07-17) Is the code ready for release? Check that the latest nightly ("Periodic") build was green. You only need to check the links that are relevant to the release that you're preparing (for example, doing a release that doesn't include LTS).
master: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/master
5.1.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.1.x/
4.4.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/4.4.x/
4.2.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/4.2.3.x/
pe-puppetdb-extensions travis builds: https://travis-ci.com/puppetlabs/pe-puppetdb-extensions/branches
Do merge-ups:
Jira (PDB-3960) Bump versions, push directly, and tag (PuppetDB 5.2.3)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-3960 Bump versions, push directly, and tag (PuppetDB 5.2.3) Issue Type: Task Assignee: Zachary Kent Created: 2018/07/10 7:59 AM Due Date: 2018/07/13 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-07-17) (if you're making the first release off a new branch you may already have done some of this) Remove the -SNASPHOT portion of the verison in project.clj in both puppetdb and pe-puppetdb-extensions. Push each repo directly to the branch you're releasing (making a PR will break things horribly) Go into the 'release-new' hipchat room to make yourself some tags ! tag puppetdb at with ! tag pe-puppetdb-extensions at with
Jira (PDB-3959) Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.3)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-3959 Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.3) Issue Type: Task Assignee: Zachary Kent Created: 2018/07/10 7:59 AM Due Date: 2018/07/10 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-07-17) 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=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Add Comment
Jira (PDB-3962) Update winston (PuppetDB 5.2.3)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-3962 Update winston (PuppetDB 5.2.3) Issue Type: Task Assignee: Zachary Kent Created: 2018/07/10 7:59 AM Due Date: 2018/07/18 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-07-17) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-3961) Check builds, promote to PE (PuppetDB 5.2.3)
Title: Message Title Kenn Hussey created an issue PuppetDB / PDB-3961 Check builds, promote to PE (PuppetDB 5.2.3) Issue Type: Task Assignee: Zachary Kent Created: 2018/07/10 7:59 AM Due Date: 2018/07/14 Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-07-17) Check that all the builds are green. Choose the tab for your branch over at https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/, then run the "manual promotion kickoff" job. Adding a new tab to Jenkins: If needed hit the + tab in the link above, select "list view", and add the following rule to the regex section that matches the build you're preparing. Example: (?!experimental).*puppetdb.*5.2.x
Jira (PUP-8995) Update Confluence and JIRA based on release (Puppet Platform 5.5.4)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8995 Update Confluence and JIRA based on release (Puppet Platform 5.5.4) Issue Type: Task Assignee: Kenn Hussey Created: 2018/07/10 7:57 AM Due Date: 2018/07/18 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-07-17) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the description a
Jira (PUP-8996) Communicate scope and timeline of next release (Puppet Platform 5.5.4)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8996 Communicate scope and timeline of next release (Puppet Platform 5.5.4) Issue Type: Task Assignee: Kenn Hussey Created: 2018/07/10 7:57 AM Due Date: 2018/07/18 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-07-17) 1) Create versions and filters for the release in in JIRA. Ensure that the filters are shared with the ‘All Employees’ group. 2) Create or update the Kanban board for the release series. Ensure that the underlying filter for the board includes issues from the release filter and add a quick filter to highlight just those issues. 3) Create Release tickets (in the Project Central project) for the Puppet Platform and puppet-agent releases, with sub-tasks for each milestone (e.g., “String Freeze”, “Stop Ship Line”, “Ready to Ship”, and “General Availability (GA)”. 4) Create release pages for the Puppet Platform and puppet-agent releases in Confluence, under the appropriate “Upcoming Releases” parent page. Make sure the pages reference the release filters, tickets, and Kanban board as needed. 5) Update the “Versions & Dependencies” pages for Puppet Platform and puppet-agent with dependency versions for releases. Format the release versions in italics and link them to their corresponding release pages. 6) Add events for the release milestone dates to Group-Platform Google calendar. Ensure the description for each event includes a link to the release page. 7) Send an email to stakeholders (e.g., puppet-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release.
Jira (PUP-8994) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.4)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8994 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.4) Issue Type: Task Assignee: Kenn Hussey Created: 2018/07/10 7:56 AM Due Date: 2018/07/16 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-07-17) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in ‘Platform Core’ HipChat room for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-8992) Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.4)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8992 Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.4) Issue Type: Task Assignee: Kenn Hussey Created: 2018/07/10 7:56 AM Due Date: 2018/07/11 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-07-17) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in HipChat) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved. Add Comment
Jira (PUP-8993) Prepare release announcement (Puppet Platform 5.5.4)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8993 Prepare release announcement (Puppet Platform 5.5.4) Issue Type: Task Assignee: Garrett Guillotte Created: 2018/07/10 7:56 AM Due Date: 2018/07/16 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-07-17) Please paste the text of the announcement in the 'Send announcement' ticket. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary. Add Comment
Jira (PUP-8991) Prepare JIRA for release (Puppet Platform 5.5.4)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8991 Prepare JIRA for release (Puppet Platform 5.5.4) Issue Type: Task Assignee: Kenn Hussey Created: 2018/07/10 7:56 AM Due Date: 2018/07/11 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2018-07-17) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 3) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 4) Update the “master” filters for Puppet Platform 5.5.4 and puppet-agent 5.5.4 to reference the “Fixed in” filters created above. 5) Update the community feedback filter for Puppet Platform X.y to reference the “Introduced in” filter created above.
Jira (PUP-8990) Puppet Platform 5.5.4 Release - 2018-07-17
Title: Message Title Kenn Hussey created an issue Puppet / PUP-8990 Puppet Platform 5.5.4 Release - 2018-07-17 Issue Type: Epic Assignee: Kenn Hussey Created: 2018/07/10 7:56 AM Due Date: 2018/07/17 Priority: Normal Reporter: Kenn Hussey Puppet Platform 5.5.4 Release - 2018-07-17 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
