Jira (PUP-8874) Extract the code & verify the module

2018-07-20 Thread Melissa Stone (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Melissa Stone commented on  PUP-8874  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Extract the code & verify the module   
 

  
 
 
 
 

 
 As there is already a repo where this code has been extracted, I simply installed the latest passing sha from puppet-agent#master, deleted the scheduled_task files that have already been extracted, then installed the puppetlabs/scheduled_task module from the forge. I then executed a scheduled task manifest to ensure it would apply as expected. I took a screen shot of the results, which I have pasted in this ticket.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8874) Extract the code & verify the module

2018-07-20 Thread Melissa Stone (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Melissa Stone updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8874  
 
 
  Extract the code & verify the module   
 

  
 
 
 
 

 
Change By: 
 Melissa Stone  
 
 
Attachment: 
 Screen Shot 2018-07-20 at 2.31.07 PM.png  
 

  
 
 
 
 

 
 
 

 
 
 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-8874) Extract the code & verify the module

2018-07-20 Thread Melissa Stone (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Melissa Stone assigned an issue to Melissa Stone  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8874  
 
 
  Extract the code & verify the module   
 

  
 
 
 
 

 
Change By: 
 Melissa Stone  
 
 
Assignee: 
 Melissa Stone  
 

  
 
 
 
 

 
 
 

 
 
 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-8874) Extract the code & verify the module

2018-05-23 Thread Austin Boyd (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Melissa Stone created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8874  
 
 
  Extract the code & verify the module   
 

  
 
 
 
 

 
Issue Type: 
  Sub-task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2018/05/23 3:44 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