Jira (FACT-620) windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms

2018-05-15 Thread Casey Williams (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Casey Williams commented on  FACT-620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms   
 

  
 
 
 
 

 
 Closing – per Eric Sorenson's reluctance, we feel the benefits of consistency here wouldn't outweigh the breakage across existing puppet code that this would cause.  
 

  
 
 
 
 

 
 
 

 
 
 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-620) windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms

2018-03-21 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-620  
 
 
  windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms   
 

  
 
 
 
 

 
Change By: 
 Branan Riley  
 
 
Fix Version/s: 
 FACT 4.0.0  
 

  
 
 
 
 

 
 
 

 
 
 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-620) windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms

2018-03-21 Thread Branan Riley (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Branan Riley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-620  
 
 
  windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms   
 

  
 
 
 
 

 
Change By: 
 Branan Riley  
 
 
Labels: 
 breaking cisco  needs_triage  netdev  triaged  windows  
 

  
 
 
 
 

 
 
 

 
 
 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-620) windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms

2018-02-21 Thread Sean McDonald (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean McDonald updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-620  
 
 
  windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms   
 

  
 
 
 
 

 
Change By: 
 Sean McDonald  
 
 
Labels: 
 cisco  needs_triage  netdev  triaged  windows  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)  
 
 

 
   
 

  
 

  
 

   





-- 
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-620) windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms

2018-02-21 Thread Sean McDonald (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sean McDonald updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-620  
 
 
  windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms   
 

  
 
 
 
 

 
Change By: 
 Sean McDonald  
 
 
Labels: 
 cisco  netdev triaged  windows  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)  
 
 

 
   
 

  
 

  
 

   





-- 
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-620) windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms

2017-05-17 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-620 
 
 
 
  windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-620) windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms

2017-05-17 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-620 
 
 
 
  windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Labels:
 
 cisco  triaged  windows 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-620) windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms

2017-05-04 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney commented on  FACT-620 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms  
 
 
 
 
 
 
 
 
 
 
When looking at the facts from all the different systems why do we have a few systems which are lower cased instead of camel cased like "windows" and "cisco-wrlinux" 
os.family : "AIX" os.family : "Darwin" os.family : "Debian" os.family : "Linux" os.family : "RedHat" os.family : "Solaris" os.family : "Suse" os.family : "cisco-wrlinux" os.family : "windows" 
os.name : "AIX" os.name : "AristaEOS" os.name : "CentOS" os.name : "CumulusLinux" os.name : "Darwin" os.name : "Debian" os.name : "Fedora" os.name : "OracleLinux" os.name : "RedHat" os.name : "SLES" os.name : "Scientific" os.name : "Solaris" os.name : "Ubuntu" os.name : "ios_xr" os.name : "nexus" os.name : "windows" 
kernel : "AIX" kernel : "Darwin" kernel : "Linux" kernel : "SunOS" kernel : "windows" 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-620) windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms

2017-05-04 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-620 
 
 
 
  windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 
 
 
 
 
 
 
 Output from facter for $::osfamily , os.name,  and $::kernel is inconsistent vs output on other platforms.I get 'windows' instead of 'Windows' as the output. os.family : "cisco-wrlinux"os.family : "windows"os.name : "ios_xr"os.name : "nexus"os.name : "windows"kernel : "windows" Other platforms give outputs such as 'Solaris' or 'RedHat' because programmers and customers picking up this fact will naturally expect its output to be consistent with other platforms.Today this has led to bug  MODULES-1203 (PR merged) which broke the concat module for our windows users - I'm concerned that we will see this problem come up time after time and also that it will impact our customers - eg if they use regexps.  Would be great if this could be addressed to improve consistencyCheers, 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (FACT-620) windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms

2017-05-04 Thread Eric Delaney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Delaney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-620 
 
 
 
  windows and cisco facter $::osfamily, os.name, and $::kernel output inconsistent vs other platforms  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Delaney 
 
 
 

Summary:
 
 windows  and cisco  facter $::osfamily , os.name,  and $::kernel output inconsistent vs other platforms 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.