Jira (FACT-1378) EC2 metadata fact is not parsed properly

2017-02-23 Thread Greg Hardy (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Greg Hardy commented on  FACT-1378 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: EC2 metadata fact is not parsed properly  
 
 
 
 
 
 
 
 
 
 
I'll check. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1378) EC2 metadata fact is not parsed properly

2017-02-07 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  FACT-1378 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: EC2 metadata fact is not parsed properly  
 
 
 
 
 
 
 
 
 
 
This may still be an issue in Facter 3. Any chance you can check? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1378) EC2 metadata fact is not parsed properly

2016-11-08 Thread Greg Hardy (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Greg Hardy commented on  FACT-1378 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: EC2 metadata fact is not parsed properly  
 
 
 
 
 
 
 
 
 
 
No IAM appear now in the API. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1378) EC2 metadata fact is not parsed properly

2016-11-08 Thread Greg Hardy (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Greg Hardy commented on  FACT-1378 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: EC2 metadata fact is not parsed properly  
 
 
 
 
 
 
 
 
 
 
curl http://169.254.169.254/latest/meta-data/ ami-id ami-launch-index ami-manifest-path block-device-mapping/ hostname instance-action instance-id instance-type local-hostname local-ipv4 mac metrics/ network/ placement/ product-codes profile public-hostname public-ipv4 public-keys/ reservation-id security-groups services/[ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1378) EC2 metadata fact is not parsed properly

2016-11-08 Thread Greg Hardy (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Greg Hardy commented on  FACT-1378 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: EC2 metadata fact is not parsed properly  
 
 
 
 
 
 
 
 
 
 
Talked with Geoff Nichols about it. He suggested talking to Maggie Dreyer/Michael Smith/Banan Riley to run it past them about the facter support. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1378) EC2 metadata fact is not parsed properly

2016-10-20 Thread Kevin Jones (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kevin Jones assigned an issue to Greg Hardy 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1378 
 
 
 
  EC2 metadata fact is not parsed properly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kevin Jones 
 
 
 

Assignee:
 
 Greg Hardy 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1378) EC2 metadata fact is not parsed properly

2016-09-11 Thread Andrew Henroid (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Henroid updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1378 
 
 
 
  EC2 metadata fact is not parsed properly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Henroid 
 
 
 

Team:
 
 Cloud & Future Tech 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1378) EC2 metadata fact is not parsed properly

2016-03-29 Thread Joshua Spence (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joshua Spence created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1378 
 
 
 
  EC2 metadata fact is not parsed properly  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 FACT 2.4.6 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/03/29 7:17 PM 
 
 
 

Environment:
 
 
Ruby 1.8.7 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Joshua Spence 
 
 
 
 
 
 
 
 
 
 
The `ec2_metadata` fact does not seem to be parsed correctly, specifically the `iam.info` subkey. I would expect the type of `$::ec2_metadata['iam']['info']` to be a hash but instead it is an array of strings. 
``` > bundle exec facter --yaml ec2_metadata Error loading fact /usr/lib/ruby/vendor_ruby/facter/macosx.rb: no such file to load – cfpropertylist ldapname is deprecated and will be removed in a future version Facter::Util::EC2.has_euca_mac? is deprecated; see the Facter::EC2 classes instead Facter::Util::EC2.has_openstack_mac? is deprecated; see the Facter::EC2 classes instead Facter::Util::EC2.has_ec2_arp? is deprecated; see the Facter::EC2 classes instead Facter::Util::EC2.can_connect? is deprecated; see the Facter::EC2 classes instead —  ec2_metadata:  ... iam:  info:  
 

" {" - " \"Code\" : \"Success\"," - " \"LastUpdated\" : \"2016-03-30T01:29:08Z\"," - "