Mock DNS for AWS

Discussion:

Mock DNS for AWS

Mike Shea

2013-02-01 20:40:17 UTC

Hi folks,

I'm writing some rspec tests using Fog.mock! and AWS DNS, and I've run into
this:

Fog::Errors::MockNotImplemented: Contributions welcome!
/Users/michael.shea/.rvm/gems/ruby-1.9.3-p194/gems/fog-1.8.0/lib/fog/core/mock.rb:34:in
`not_implemented'
/Users/michael.shea/.rvm/gems/ruby-1.9.3-p194/gems/fog-1.8.0/lib/fog/core/service.rb:111:in
`list_resource_record_sets'
/Users/michael.shea/.rvm/gems/ruby-1.9.3-p194/gems/fog-1.8.0/lib/fog/aws/models/dns/records.rb:31:in
`all'
/Users/michael.shea/.rvm/gems/ruby-1.9.3-p194/gems/fog-1.8.0/lib/fog/core/collection.rb:130:in
`lazy_load'
/Users/michael.shea/.rvm/gems/ruby-1.9.3-p194/gems/fog-1.8.0/lib/fog/core/collection.rb:18:in
`each'

I would like to help fix it, but I just want to make sure that I'm not
redoing something that has already been done, or missing something :). It
looks to me like I need to implement
Fog::DNS::AWS::Mock.list_resource_record_sets. I've already written an
implementation that is good enough for my own use cases, but I'm sure that
it will not cover everything (I'm only using it to test that some CNAME
records my program creates did, in fact, get created).

So - unless somebody here lets me know that I'm on the wrong track entirely
or that this work is already done, I'm going to fork fog and get to work.

I'm using fog-1.8.0

Thanks!

Mike Shea.

--
You received this message because you are subscribed to the Google Groups "ruby-fog" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ruby-fog+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.

geemus (Wesley Beary)

2013-02-01 21:11:22 UTC

Permalink

I think you hit the nail on the head. It is to-be-done but isn't done yet.
I think making sure it covers your usage (and the existing test suite
within fog) is a great start and we can always expand from there if/when
needed. Definitely let me/us know if you have any questions along the way
and we'll be happy to help out.
Thanks!
wes

Post by Mike Shea
Hi folks,
I'm writing some rspec tests using Fog.mock! and AWS DNS, and I've run
Fog::Errors::MockNotImplemented: Contributions welcome!
/Users/michael.shea/.rvm/gems/ruby-1.9.3-p194/gems/fog-1.8.0/lib/fog/core/mock.rb:34:in
`not_implemented'
/Users/michael.shea/.rvm/gems/ruby-1.9.3-p194/gems/fog-1.8.0/lib/fog/core/service.rb:111:in
`list_resource_record_sets'
/Users/michael.shea/.rvm/gems/ruby-1.9.3-p194/gems/fog-1.8.0/lib/fog/aws/models/dns/records.rb:31:in
`all'
/Users/michael.shea/.rvm/gems/ruby-1.9.3-p194/gems/fog-1.8.0/lib/fog/core/collection.rb:130:in
`lazy_load'
/Users/michael.shea/.rvm/gems/ruby-1.9.3-p194/gems/fog-1.8.0/lib/fog/core/collection.rb:18:in
`each'
I would like to help fix it, but I just want to make sure that I'm not
redoing something that has already been done, or missing something :). It
looks to me like I need to implement
Fog::DNS::AWS::Mock.list_resource_record_sets. I've already written an
implementation that is good enough for my own use cases, but I'm sure that
it will not cover everything (I'm only using it to test that some CNAME
records my program creates did, in fact, get created).
So - unless somebody here lets me know that I'm on the wrong track
entirely or that this work is already done, I'm going to fork fog and get
to work.
I'm using fog-1.8.0
Thanks!
Mike Shea.
--
You received this message because you are subscribed to the Google Groups "ruby-fog" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/groups/opt_out.

Tim McGilchrist

2013-03-05 00:06:29 UTC

Permalink

Hi Mike,

I'm hitting the same mock not implemented issue, and wanted to check if
you've submitted a pull request for it yet?

Cheers,
Tim McGilchrist