Issue #22783 has been reported by Ari Pringle. ---------------------------------------- Feature #22783: Use latest EC2 metadata https://projects.puppetlabs.com/issues/22783
* Author: Ari Pringle * Status: Unreviewed * Priority: Normal * Assignee: * Category: * Target version: * Keywords: * Branch: * Affected Facter version: ---------------------------------------- I'm working on a project that requires a more updated version of the EC2 metadata to be pulled than what is currently available in the stable facter branch. There was a commit merged into the master branch 8 months ago that made the necessary change, but it has yet to be merged into stable. I was wondering what it might take to get this merged to stable, or if it would make more sense for me to create a PR that just includes the specific change that I need? The existing commit that includes the change: https://github.com/puppetlabs/facter/commit/ce18220fcb93e13ff459d2b4abcf18a96c658b87 The file on the master branch: https://github.com/puppetlabs/facter/blob/master/spec/unit/ec2_spec.rb The file on the stable branch: https://github.com/puppetlabs/facter/blob/stable/spec/unit/ec2_spec.rb For my particular use case, the only change that needs to be made is that "/2008-02-01/meta-data/" becomes "/latest/meta-data") -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
