Jira (PUP-8821) Package module into puppet-agent
Title: Message Title Melissa Stone created an issue Puppet / PUP-8821 Package module into puppet-agent Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Add component files for your module to puppet-agent. * Create configs/components/module-puppetlabs-_core.json * Create configs/components/module-puppetlabs-_core.rb * Add your component to the list of vendored modules in configs/projects/puppet-agent.rb * Ensure PR testing works, and ensure ci is green once your PR is merged in * Create a module promotion job in ci-job-configs that is triggered by the forge module ship job for your module For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8823) Move all outstanding PUP tickets to Modules
Title: Message Title Melissa Stone created an issue Puppet / PUP-8823 Move all outstanding PUP tickets to Modules Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Move all tickets relating to this module out of the PUP project and into the MODULES project, excluding the ticket for the module extraction. * Set 'team' to 'Coremunity' * Add a component label that matches the module name For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8818) Extract the code & verify the module
Title: Message Title Melissa Stone created an issue Puppet / PUP-8818 Extract the code & verify the module Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Extract the code from puppet and into your module. You'll be copying the existing file structure into your module, but you will need to keep an eye out for any implicit dependencies that only really manifest in the code. * Generate a new module skeleton using PDK * Copy existing files from puppet to the new module, preserving the existing file layout * Ensure the unit tests pass successfully using `pdk test unit` * Ensure rubocop violations are fixed using `pdk validate` * Circle back and make sure the unit tests still pass after fixing any rubocop violations * Migrate the acceptance tests to use beaker-rspec, you'll need to add a system_test group to .sync.yml, create a default nodeset, move the location of the tests, and change them to use an rspec like syntax. * Once acceptance, spec, and rubocop tests all pass successfully, you'll want to build and verify your module to make sure the code is picked up and runs succesfully when installed as an independent module. * Make sure the readme is filled out fully with details on your module. For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing
Jira (PUP-8811) Extract the code & verify the module
Title: Message Title Melissa Stone created an issue Puppet / PUP-8811 Extract the code & verify the module Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Extract the code from puppet and into your module. You'll be copying the existing file structure into your module, but you will need to keep an eye out for any implicit dependencies that only really manifest in the code. * Generate a new module skeleton using PDK * Copy existing files from puppet to the new module, preserving the existing file layout * Ensure the unit tests pass successfully using `pdk test unit` * Ensure rubocop violations are fixed using `pdk validate` * Circle back and make sure the unit tests still pass after fixing any rubocop violations * Migrate the acceptance tests to use beaker-rspec, you'll need to add a system_test group to .sync.yml, create a default nodeset, move the location of the tests, and change them to use an rspec like syntax. * Once acceptance, spec, and rubocop tests all pass successfully, you'll want to build and verify your module to make sure the code is picked up and runs succesfully when installed as an independent module. * Make sure the readme is filled out fully with details on your module. For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing
Jira (PUP-8816) Move all outstanding PUP tickets to Modules
Title: Message Title Melissa Stone created an issue Puppet / PUP-8816 Move all outstanding PUP tickets to Modules Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Move all tickets relating to this module out of the PUP project and into the MODULES project, excluding the ticket for the module extraction. * Set 'team' to 'Coremunity' * Add a component label that matches the module name For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8817) Create the github repo
Title: Message Title Melissa Stone created an issue Puppet / PUP-8817 Create the github repo Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Create a public github repo in the puppetlabs namespace * The name should follow the format github.com/puppetlabs/puppetlabs-_core * Grant additional permissions so other folks/automation can access the new repo as well * Enable Travis/AppVeyor where appropriate * Turn off additional repo features we do not use For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8809) Move all outstanding PUP tickets to Modules
Title: Message Title Melissa Stone created an issue Puppet / PUP-8809 Move all outstanding PUP tickets to Modules Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Move all tickets relating to this module out of the PUP project and into the MODULES project, excluding the ticket for the module extraction. * Set 'team' to 'Coremunity' * Add a component label that matches the module name For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8814) Package module into puppet-agent
Title: Message Title Melissa Stone created an issue Puppet / PUP-8814 Package module into puppet-agent Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Add component files for your module to puppet-agent. * Create configs/components/module-puppetlabs-_core.json * Create configs/components/module-puppetlabs-_core.rb * Add your component to the list of vendored modules in configs/projects/puppet-agent.rb * Ensure PR testing works, and ensure ci is green once your PR is merged in * Create a module promotion job in ci-job-configs that is triggered by the forge module ship job for your module For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8831) Create the github repo
Title: Message Title Melissa Stone created an issue Puppet / PUP-8831 Create the github repo Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Create a public github repo in the puppetlabs namespace * The name should follow the format github.com/puppetlabs/puppetlabs-_core * Grant additional permissions so other folks/automation can access the new repo as well * Enable Travis/AppVeyor where appropriate * Turn off additional repo features we do not use For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8810) Create the github repo
Title: Message Title Melissa Stone created an issue Puppet / PUP-8810 Create the github repo Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Create a public github repo in the puppetlabs namespace * The name should follow the format github.com/puppetlabs/puppetlabs-_core * Grant additional permissions so other folks/automation can access the new repo as well * Enable Travis/AppVeyor where appropriate * Turn off additional repo features we do not use For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8825) Extract the code & verify the module
Title: Message Title Melissa Stone created an issue Puppet / PUP-8825 Extract the code & verify the module Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Extract the code from puppet and into your module. You'll be copying the existing file structure into your module, but you will need to keep an eye out for any implicit dependencies that only really manifest in the code. * Generate a new module skeleton using PDK * Copy existing files from puppet to the new module, preserving the existing file layout * Ensure the unit tests pass successfully using `pdk test unit` * Ensure rubocop violations are fixed using `pdk validate` * Circle back and make sure the unit tests still pass after fixing any rubocop violations * Migrate the acceptance tests to use beaker-rspec, you'll need to add a system_test group to .sync.yml, create a default nodeset, move the location of the tests, and change them to use an rspec like syntax. * Once acceptance, spec, and rubocop tests all pass successfully, you'll want to build and verify your module to make sure the code is picked up and runs succesfully when installed as an independent module. * Make sure the readme is filled out fully with details on your module. For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing
Jira (PUP-8815) Remove type/provider code from puppet
Title: Message Title Melissa Stone created an issue Puppet / PUP-8815 Remove type/provider code from puppet Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Remove all extracted files from the puppet repo. For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8804) Extract the code & verify the module
Title: Message Title Melissa Stone created an issue Puppet / PUP-8804 Extract the code & verify the module Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Extract the code from puppet and into your module. You'll be copying the existing file structure into your module, but you will need to keep an eye out for any implicit dependencies that only really manifest in the code. * Generate a new module skeleton using PDK * Copy existing files from puppet to the new module, preserving the existing file layout * Ensure the unit tests pass successfully using `pdk test unit` * Ensure rubocop violations are fixed using `pdk validate` * Circle back and make sure the unit tests still pass after fixing any rubocop violations * Migrate the acceptance tests to use beaker-rspec, you'll need to add a system_test group to .sync.yml, create a default nodeset, move the location of the tests, and change them to use an rspec like syntax. * Once acceptance, spec, and rubocop tests all pass successfully, you'll want to build and verify your module to make sure the code is picked up and runs succesfully when installed as an independent module. * Make sure the readme is filled out fully with details on your module. For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing
Jira (PUP-8808) Remove type/provider code from puppet
Title: Message Title Melissa Stone created an issue Puppet / PUP-8808 Remove type/provider code from puppet Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Remove all extracted files from the puppet repo. For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8805) Create the CI pipeline
Title: Message Title Melissa Stone created an issue Puppet / PUP-8805 Create the CI pipeline Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Create the CI pipeline for your new module. * Create an entry for your module in https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/jenkins-master-prod-1/projects/modules-unified.yaml * Generate experimental jobs and run the adhoc pipeline targeting either your branch if your main module PR hasn't been merged, or the puppetlabs repo if it has. Ensure the adhoc pipeline runs green. * Create a new tab view for your new module once your PR has been merged and the jobs have been created For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8794) Remove type/provider code from puppet
Title: Message Title Melissa Stone created an issue Puppet / PUP-8794 Remove type/provider code from puppet Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Remove all extracted files from the puppet repo. For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8780) Remove type/provider code from puppet
Title: Message Title Melissa Stone created an issue Puppet / PUP-8780 Remove type/provider code from puppet Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:42 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Remove all extracted files from the puppet repo. For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8807) Package module into puppet-agent
Title: Message Title Melissa Stone created an issue Puppet / PUP-8807 Package module into puppet-agent Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Add component files for your module to puppet-agent. * Create configs/components/module-puppetlabs-_core.json * Create configs/components/module-puppetlabs-_core.rb * Add your component to the list of vendored modules in configs/projects/puppet-agent.rb * Ensure PR testing works, and ensure ci is green once your PR is merged in * Create a module promotion job in ci-job-configs that is triggered by the forge module ship job for your module For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8775) Create the github repo
Title: Message Title Melissa Stone created an issue Puppet / PUP-8775 Create the github repo Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:42 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Create a public github repo in the puppetlabs namespace * The name should follow the format github.com/puppetlabs/puppetlabs-_core * Grant additional permissions so other folks/automation can access the new repo as well * Enable Travis/AppVeyor where appropriate * Turn off additional repo features we do not use For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8785) Release 1.0.0 to the forge
Title: Message Title Melissa Stone created an issue Puppet / PUP-8785 Release 1.0.0 to the forge Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:42 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Release your module to the forge. The first release will need to be manual. * Create the module tarball to release \\git clone https://github.com/puppetlabs/module /path/to/fresh/directory \\git checkout tags/ \\COPYFILE_DISABLE=1 puppet module build \\tar -tf module-name.tar.gz \\ * Log into the forge as 'puppetlabs', get the password from Melissa or Hunner or 1password * Upload the tarball For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing
Jira (PUP-8806) Release 1.0.0 to the forge
Title: Message Title Melissa Stone created an issue Puppet / PUP-8806 Release 1.0.0 to the forge Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Release your module to the forge. The first release will need to be manual. * Create the module tarball to release \\git clone https://github.com/puppetlabs/module /path/to/fresh/directory \\git checkout tags/ \\COPYFILE_DISABLE=1 puppet module build \\tar -tf module-name.tar.gz \\ * Log into the forge as 'puppetlabs', get the password from Melissa or Hunner or 1password * Upload the tarball For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing
Jira (PUP-8782) Create the github repo
Title: Message Title Melissa Stone created an issue Puppet / PUP-8782 Create the github repo Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:42 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Create a public github repo in the puppetlabs namespace * The name should follow the format github.com/puppetlabs/puppetlabs-_core * Grant additional permissions so other folks/automation can access the new repo as well * Enable Travis/AppVeyor where appropriate * Turn off additional repo features we do not use For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8796) Create the github repo
Title: Message Title Melissa Stone created an issue Puppet / PUP-8796 Create the github repo Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Create a public github repo in the puppetlabs namespace * The name should follow the format github.com/puppetlabs/puppetlabs-_core * Grant additional permissions so other folks/automation can access the new repo as well * Enable Travis/AppVeyor where appropriate * Turn off additional repo features we do not use For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8797) Extract the code & verify the module
Title: Message Title Melissa Stone created an issue Puppet / PUP-8797 Extract the code & verify the module Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Extract the code from puppet and into your module. You'll be copying the existing file structure into your module, but you will need to keep an eye out for any implicit dependencies that only really manifest in the code. * Generate a new module skeleton using PDK * Copy existing files from puppet to the new module, preserving the existing file layout * Ensure the unit tests pass successfully using `pdk test unit` * Ensure rubocop violations are fixed using `pdk validate` * Circle back and make sure the unit tests still pass after fixing any rubocop violations * Migrate the acceptance tests to use beaker-rspec, you'll need to add a system_test group to .sync.yml, create a default nodeset, move the location of the tests, and change them to use an rspec like syntax. * Once acceptance, spec, and rubocop tests all pass successfully, you'll want to build and verify your module to make sure the code is picked up and runs succesfully when installed as an independent module. * Make sure the readme is filled out fully with details on your module. For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing
Jira (PUP-8777) Create the CI pipeline
Title: Message Title Melissa Stone created an issue Puppet / PUP-8777 Create the CI pipeline Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:42 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Create the CI pipeline for your new module. * Create an entry for your module in https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/jenkins-master-prod-1/projects/modules-unified.yaml * Generate experimental jobs and run the adhoc pipeline targeting either your branch if your main module PR hasn't been merged, or the puppetlabs repo if it has. Ensure the adhoc pipeline runs green. * Create a new tab view for your new module once your PR has been merged and the jobs have been created For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8778) Release 1.0.0 to the forge
Title: Message Title Melissa Stone created an issue Puppet / PUP-8778 Release 1.0.0 to the forge Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:42 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Release your module to the forge. The first release will need to be manual. * Create the module tarball to release git clone https://github.com/puppetlabs/module /path/to/fresh/directorygit checkout tags/COPYFILE_DISABLE=1 puppet module buildtar -tf module-name.tar.gz * Log into the forge as 'puppetlabs', get the password from Melissa or Hunner or 1password * Upload the tarball For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing
Jira (PUP-8800) Package module into puppet-agent
Title: Message Title Melissa Stone created an issue Puppet / PUP-8800 Package module into puppet-agent Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Add component files for your module to puppet-agent. * Create configs/components/module-puppetlabs-_core.json * Create configs/components/module-puppetlabs-_core.rb * Add your component to the list of vendored modules in configs/projects/puppet-agent.rb * Ensure PR testing works, and ensure ci is green once your PR is merged in * Create a module promotion job in ci-job-configs that is triggered by the forge module ship job for your module For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8786) Package module into puppet-agent
Title: Message Title Melissa Stone created an issue Puppet / PUP-8786 Package module into puppet-agent Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:42 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Add component files for your module to puppet-agent. * Create configs/components/module-puppetlabs-_core.json * Create configs/components/module-puppetlabs-_core.rb * Add your component to the list of vendored modules in configs/projects/puppet-agent.rb * Ensure PR testing works, and ensure ci is green once your PR is merged in * Create a module promotion job in ci-job-configs that is triggered by the forge module ship job for your module For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8783) Extract the code & verify the module
Title: Message Title Melissa Stone created an issue Puppet / PUP-8783 Extract the code & verify the module Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:42 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Extract the code from puppet and into your module. You'll be copying the existing file structure into your module, but you will need to keep an eye out for any implicit dependencies that only really manifest in the code. * Generate a new module skeleton using PDK * Copy existing files from puppet to the new module, preserving the existing file layout * Ensure the unit tests pass successfully using `pdk test unit` * Ensure rubocop violations are fixed using `pdk validate` * Circle back and make sure the unit tests still pass after fixing any rubocop violations * Migrate the acceptance tests to use beaker-rspec, you'll need to add a system_test group to .sync.yml, create a default nodeset, move the location of the tests, and change them to use an rspec like syntax. * Once acceptance, spec, and rubocop tests all pass successfully, you'll want to build and verify your module to make sure the code is picked up and runs succesfully when installed as an independent module. * Make sure the readme is filled out fully with details on your module. For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing
Jira (PUP-8784) Create the CI pipeline
Title: Message Title Melissa Stone created an issue Puppet / PUP-8784 Create the CI pipeline Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:42 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Create the CI pipeline for your new module. * Create an entry for your module in https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/jenkins-master-prod-1/projects/modules-unified.yaml * Generate experimental jobs and run the adhoc pipeline targeting either your branch if your main module PR hasn't been merged, or the puppetlabs repo if it has. Ensure the adhoc pipeline runs green. * Create a new tab view for your new module once your PR has been merged and the jobs have been created For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8793) Package module into puppet-agent
Title: Message Title Melissa Stone created an issue Puppet / PUP-8793 Package module into puppet-agent Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Add component files for your module to puppet-agent. * Create configs/components/module-puppetlabs-_core.json * Create configs/components/module-puppetlabs-_core.rb * Add your component to the list of vendored modules in configs/projects/puppet-agent.rb * Ensure PR testing works, and ensure ci is green once your PR is merged in * Create a module promotion job in ci-job-configs that is triggered by the forge module ship job for your module For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8799) Release 1.0.0 to the forge
Title: Message Title Melissa Stone created an issue Puppet / PUP-8799 Release 1.0.0 to the forge Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Release your module to the forge. The first release will need to be manual. * Create the module tarball to release \\git clone https://github.com/puppetlabs/module /path/to/fresh/directory \\git checkout tags/ \\COPYFILE_DISABLE=1 puppet module build \\tar -tf module-name.tar.gz \\ * Log into the forge as 'puppetlabs', get the password from Melissa or Hunner or 1password * Upload the tarball For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing
Jira (PUP-8792) Release 1.0.0 to the forge
Title: Message Title Melissa Stone created an issue Puppet / PUP-8792 Release 1.0.0 to the forge Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Release your module to the forge. The first release will need to be manual. * Create the module tarball to release \\git clone https://github.com/puppetlabs/module /path/to/fresh/directory \\git checkout tags/ \\COPYFILE_DISABLE=1 puppet module build \\tar -tf module-name.tar.gz \\ * Log into the forge as 'puppetlabs', get the password from Melissa or Hunner or 1password * Upload the tarball For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing
Jira (PUP-8801) Remove type/provider code from puppet
Title: Message Title Melissa Stone created an issue Puppet / PUP-8801 Remove type/provider code from puppet Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Remove all extracted files from the puppet repo. For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8795) Move all outstanding PUP tickets to Modules
Title: Message Title Melissa Stone created an issue Puppet / PUP-8795 Move all outstanding PUP tickets to Modules Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Move all tickets relating to this module out of the PUP project and into the MODULES project, excluding the ticket for the module extraction. * Set 'team' to 'Coremunity' * Add a component label that matches the module name For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8798) Create the CI pipeline
Title: Message Title Melissa Stone created an issue Puppet / PUP-8798 Create the CI pipeline Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Create the CI pipeline for your new module. * Create an entry for your module in https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/jenkins-master-prod-1/projects/modules-unified.yaml * Generate experimental jobs and run the adhoc pipeline targeting either your branch if your main module PR hasn't been merged, or the puppetlabs repo if it has. Ensure the adhoc pipeline runs green. * Create a new tab view for your new module once your PR has been merged and the jobs have been created For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8776) Extract the code & verify the module
Title: Message Title Melissa Stone created an issue Puppet / PUP-8776 Extract the code & verify the module Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:42 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Extract the code from puppet and into your module. You'll be copying the existing file structure into your module, but you will need to keep an eye out for any implicit dependencies that only really manifest in the code. * Generate a new module skeleton using PDK * Copy existing files from puppet to the new module, preserving the existing file layout * Ensure the unit tests pass successfully using `pdk test unit` * Ensure rubocop violations are fixed using `pdk validate` * Circle back and make sure the unit tests still pass after fixing any rubocop violations * Migrate the acceptance tests to use beaker-rspec, you'll need to add a system_test group to .sync.yml, create a default nodeset, move the location of the tests, and change them to use an rspec like syntax. * Once acceptance, spec, and rubocop tests all pass successfully, you'll want to build and verify your module to make sure the code is picked up and runs succesfully when installed as an independent module. * Make sure the readme is filled out fully with details on your module. For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing
Jira (PUP-8779) Package module into puppet-agent
Title: Message Title Melissa Stone created an issue Puppet / PUP-8779 Package module into puppet-agent Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:42 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Add component files for your module to puppet-agent. * Create configs/components/module-puppetlabs-_core.json * Create configs/components/module-puppetlabs-_core.rb * Add your component to the list of vendored modules in configs/projects/puppet-agent.rb * Ensure PR testing works, and ensure ci is green once your PR is merged in * Create a module promotion job in ci-job-configs that is triggered by the forge module ship job for your module For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8791) Create the CI pipeline
Title: Message Title Melissa Stone created an issue Puppet / PUP-8791 Create the CI pipeline Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Create the CI pipeline for your new module. * Create an entry for your module in https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/jenkins-master-prod-1/projects/modules-unified.yaml * Generate experimental jobs and run the adhoc pipeline targeting either your branch if your main module PR hasn't been merged, or the puppetlabs repo if it has. Ensure the adhoc pipeline runs green. * Create a new tab view for your new module once your PR has been merged and the jobs have been created For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8788) Move all outstanding PUP tickets to Modules
Title: Message Title Melissa Stone created an issue Puppet / PUP-8788 Move all outstanding PUP tickets to Modules Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Move all tickets relating to this module out of the PUP project and into the MODULES project, excluding the ticket for the module extraction. * Set 'team' to 'Coremunity' * Add a component label that matches the module name For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8790) Extract the code & verify the module
Title: Message Title Melissa Stone created an issue Puppet / PUP-8790 Extract the code & verify the module Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Extract the code from puppet and into your module. You'll be copying the existing file structure into your module, but you will need to keep an eye out for any implicit dependencies that only really manifest in the code. * Generate a new module skeleton using PDK * Copy existing files from puppet to the new module, preserving the existing file layout * Ensure the unit tests pass successfully using `pdk test unit` * Ensure rubocop violations are fixed using `pdk validate` * Circle back and make sure the unit tests still pass after fixing any rubocop violations * Migrate the acceptance tests to use beaker-rspec, you'll need to add a system_test group to .sync.yml, create a default nodeset, move the location of the tests, and change them to use an rspec like syntax. * Once acceptance, spec, and rubocop tests all pass successfully, you'll want to build and verify your module to make sure the code is picked up and runs succesfully when installed as an independent module. * Make sure the readme is filled out fully with details on your module. For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing
Jira (PUP-8787) Remove type/provider code from puppet
Title: Message Title Melissa Stone created an issue Puppet / PUP-8787 Remove type/provider code from puppet Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Remove all extracted files from the puppet repo. For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8802) Move all outstanding PUP tickets to Modules
Title: Message Title Melissa Stone created an issue Puppet / PUP-8802 Move all outstanding PUP tickets to Modules Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Move all tickets relating to this module out of the PUP project and into the MODULES project, excluding the ticket for the module extraction. * Set 'team' to 'Coremunity' * Add a component label that matches the module name For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8803) Create the github repo
Title: Message Title Melissa Stone created an issue Puppet / PUP-8803 Create the github repo Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Create a public github repo in the puppetlabs namespace * The name should follow the format github.com/puppetlabs/puppetlabs-_core * Grant additional permissions so other folks/automation can access the new repo as well * Enable Travis/AppVeyor where appropriate * Turn off additional repo features we do not use For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8781) Move all outstanding PUP tickets to Modules
Title: Message Title Melissa Stone created an issue Puppet / PUP-8781 Move all outstanding PUP tickets to Modules Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:42 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Move all tickets relating to this module out of the PUP project and into the MODULES project, excluding the ticket for the module extraction. * Set 'team' to 'Coremunity' * Add a component label that matches the module name For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-8789) Create the github repo
Title: Message Title Melissa Stone created an issue Puppet / PUP-8789 Create the github repo Issue Type: Sub-task Assignee: Unassigned Created: 2018/05/23 3:43 PM Labels: csv-import Priority: Normal Reporter: Melissa Stone Create a public github repo in the puppetlabs namespace * The name should follow the format github.com/puppetlabs/puppetlabs-_core * Grant additional permissions so other folks/automation can access the new repo as well * Enable Travis/AppVeyor where appropriate * Turn off additional repo features we do not use For details, see https://docs.google.com/document/d/1v00xgnfnowAqedKZm-GzSjLYD5rRhToQicrk9Y1MK2E/edit?usp=sharing Add Comment
Jira (PUP-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Austin Boyd updated an issue Puppet / PUP-3238 puppet reports "end of file reached" if server closes HTTP connection Change By: Austin Boyd Labels: LTS-Triage jira_escalated Zendesk Ticket IDs: 28991 Zendesk Ticket Count: 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 (PUP-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Austin Boyd updated an issue Puppet / PUP-3238 puppet reports "end of file reached" if server closes HTTP connection Change By: Austin Boyd Labels: LTS-Triage jira_escalated 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-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Austin Boyd updated an issue Puppet / PUP-3238 puppet reports "end of file reached" if server closes HTTP connection Change By: Austin Boyd Zendesk Ticket IDs: 28991 Zendesk Ticket Count: 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 (PDB-3508) Create an actual "node purge" command
Title: Message Title Austin Boyd updated an issue PuppetDB / PDB-3508 Create an actual "node purge" command Change By: Austin Boyd Labels: jira_escalated Zendesk Ticket IDs: 28024 Zendesk Ticket Count: 1 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-8143) Some Solaris Init services are not functional with Puppet 5
Title: Message Title Austin Boyd updated an issue Puppet / PUP-8143 Some Solaris Init services are not functional with Puppet 5 Change By: Austin Boyd Labels: jira_escalated Zendesk Ticket IDs: 28070 Zendesk Ticket Count: 1 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-8167) Service SMF provider tries to stop absent service
Title: Message Title Austin Boyd updated an issue Puppet / PUP-8167 Service SMF provider tries to stop absent service Change By: Austin Boyd Zendesk Ticket IDs: 27974, 28092 Zendesk Ticket Count: 2 1 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-8167) Service SMF provider tries to stop absent service
Title: Message Title Austin Boyd updated an issue Puppet / PUP-8167 Service SMF provider tries to stop absent service Change By: Austin Boyd Labels: jira_escalated Zendesk Ticket IDs: 28092 Zendesk Ticket Count: 1 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-8167) Service SMF provider tries to stop absent service
Title: Message Title Austin Boyd updated an issue Puppet / PUP-8167 Service SMF provider tries to stop absent service Change By: Austin Boyd Zendesk Ticket IDs: 27974, 28092 Zendesk Ticket Count: 1 2 Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8167) Service SMF provider tries to stop absent service
Title: Message Title Austin Boyd updated an issue Puppet / PUP-8167 Service SMF provider tries to stop absent service Change By: Austin Boyd Zendesk Ticket IDs: 28092 Zendesk Ticket Count: 1 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-8167) Service SMF provider tries to stop absent service
Title: Message Title Austin Boyd updated an issue Puppet / PUP-8167 Service SMF provider tries to stop absent service Change By: Austin Boyd Labels: jira_escalated 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-8143) Some Solaris Init services are not functional with Puppet 5
Title: Message Title Austin Boyd updated an issue Puppet / PUP-8143 Some Solaris Init services are not functional with Puppet 5 Change By: Austin Boyd Zendesk Ticket IDs: 28070 Zendesk Ticket Count: 1 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-8143) Some Solaris Init services are not functional with Puppet 5
Title: Message Title Austin Boyd updated an issue Puppet / PUP-8143 Some Solaris Init services are not functional with Puppet 5 Change By: Austin Boyd Labels: jira_escalated 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-3508) Create an actual "node purge" command
Title: Message Title Austin Boyd updated an issue PuppetDB / PDB-3508 Create an actual "node purge" command Change By: Austin Boyd Zendesk Ticket IDs: 28024 Zendesk Ticket Count: 1 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-3508) Create an actual "node purge" command
Title: Message Title Austin Boyd updated an issue PuppetDB / PDB-3508 Create an actual "node purge" command Change By: Austin Boyd Labels: jira_escalated 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-3314) Create an activemq queue extraction tool
Title: Message Title Austin Boyd updated an issue PuppetDB / PDB-3314 Create an activemq queue extraction tool Change By: Austin Boyd Sprint: SE Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3314) Create an activemq queue extraction tool
Title: Message Title Austin Boyd updated an issue PuppetDB / PDB-3314 Create an activemq queue extraction tool Change By: Austin Boyd Sprint: SE Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
