Jira (PUP-5534) (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /environments/*/modules/*/files/*

2017-05-16 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5534 
 
 
 
  (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /environments/*/modules/*/files/*  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Labels:
 
 triaged 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (PUP-5534) (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /environments/*/modules/*/files/*

2016-02-01 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5534 
 
 
 
  (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /environments/*/modules/*/files/*  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

QA Risk Assessment Reason:
 
 This is an end-to-end type of behavior. Verifying this ensures various supporting features are working. 
 
 
 

QA Risk Assessment:
 
 High 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-5534) (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /environments/*/modules/*/files/*

2016-01-25 Thread Erik Dasher (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Dasher updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5534 
 
 
 
  (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /environments/*/modules/*/files/*  
 
 
 
 
 
 
 
 
 

Change By:
 
 Erik Dasher 
 
 
 

QA Contact:
 
 Sean Griffin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-5534) (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /environments/*/modules/*/files/*

2016-01-14 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson commented on  PUP-5534 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /environments/*/modules/*/files/*  
 
 
 
 
 
 
 
 
 
 
After further tweaks and f2f with Sean, this story is now an accurate reflection of the requirements. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-5534) (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /environments/*/modules/*/files/*

2016-01-14 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5534 
 
 
 
  (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /environments/*/modules/*/files/*  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Summary:
 
 (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in < environment codedir >/ environments/*/ modules/*/files/* 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.