Thanks Gareth, that looks pretty much like the refactoring I intended to do to converts tag facts from cli to sdk.
I have a bit of an upjumped problem at work that has me distracted from integrating puppet and AWS at the moment, but once that's resolved, I'll start curating a list of sdk available information that may be a good list to compose into a module. Sent from my iPhone > On Apr 19, 2015, at 9:12 AM, Gareth Rushgrove <gar...@morethanseven.net> > wrote: > >> On 19 April 2015 at 04:02, Peter Foley <pe...@ifoley.id.au> wrote: >> Hi Phil, >> >>> New custom facts can be distributed as Puppet modules. See >>> https://docs.puppetlabs.com/guides/plugins_in_modules.html. If you have a >>> concrete set of facts you'd like to propose, you can follow up with them or >>> put them up as a PR to Facter, but there's a good chance we'll ask that you >>> release them as a module instead. It depends on what function the facts are >>> trying to fulfill. >> >> >> If your proposed facts don't make it into the facter core set of facts could >> I suggest rather than creating a new module you develop a pull request >> against the puppetlabs-aws module [1] which is currently being worked on. >> This module already requires the aws-sdk-core ruby gem you mentioned. >> >> [1] - https://github.com/puppetlabs/puppetlabs-aws > > You might also be interested in > https://github.com/mrzarquon/puppet-ec2tags, which exposes tags on an > EC2 instance and uses the aws-sdk to do so. You could also use this as > a basis for a separate module exposing other facts based on API calls. > > Their are a number of things like this available from the API but not > from the metadata. I'm unsure whether these would be better as facts > in the AWS module, or as separate modules (maybe with a dependency > from the AWS module). My gut feeling is the later. > > Gareth > >> Peter >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-dev+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-dev/83c20dee-01a3-48d7-bc78-a2f99781b6d8%40googlegroups.com. >> >> For more options, visit https://groups.google.com/d/optout. > > > > -- > Gareth Rushgrove > @garethr > > devopsweekly.com > morethanseven.net > garethrushgrove.com > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Puppet Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-dev/Or0ZxTnoFxU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-dev/CAFi_6yJTN_UPe-1hegP%3D4n4DWqAerUVygJkyWYCJnUvvjb2NjA%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/BC7C017C-6D39-4C24-AF85-ADA61CDF9465%40gmail.com. For more options, visit https://groups.google.com/d/optout.
