Nice. I'll look out for your packer project. I've been using it to build our vagrant boxes, but haven't yet built any for vSphere or external cloud.
I'm getting this error: ruby/2.1.0/gems/aws-sdk-1.42.0/lib/aws/core/resource.rb:238:in `rescue in block in define_attribute_getter': unable to find the image (AWS::Core::Resource::NotFound) Are your AMI's public? Gist: https://gist.github.com/brettswift/176b802bfe31dae369e9 Using your sample project, if I include the puppetlabs_spec_helper in the Gemfile, it doesn't error but completes rather quickly saying there are no tests (obviously). But it doesn't bawk on any ec2 configuration. On Tuesday, 7 October 2014 08:43:45 UTC-6, Ken Barber wrote: > > > That's great Ken. > > > > I'll have a look. My .fog file was correct but I was missing that > > ec2.yaml. > > > > I get the user experience thing, it'll evolve and I'll help if I can. > > > > Would I be right to assume you built your images with packer? > > All of those images predate packer, but we're using packer now. For > example my colleague Wyatt is about to add Debian 7 testing using a > packer template he has developed. So going forward yes, packer is the > trick. > > ken. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/abdbbcfe-b23d-4eb6-8e4c-0f53b68ac6a3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
