New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DNSimple API authentication #24

Closed
billmoritz opened this Issue Nov 12, 2014 · 5 comments

Comments

Projects
None yet
4 participants
@billmoritz

billmoritz commented Nov 12, 2014

The username / password method of authentication used by this cookbook will log you out of the console. If you have many servers using this cookbook it renders the https://dnsimple.com web ui completely useless. After contacting support over there they applied a temp fix and suggested that I switch to the token authentication.

Maybe we should switch from Fog to https://github.com/aetrion/dnsimple-ruby#api-token

@martinisoft

This comment has been minimized.

Member

martinisoft commented Mar 6, 2015

Hi @billmoritz

Sorry for the late reply here. We are planning to make 2.0 of this cookbook use the soon to be released dnsimple-ruby gem 2.0 which drops the need for the fog gem. In fact, the current fog gem conflicts with the latest Chef release so you cannot use 12.1.0 with this cookbook right now due to that dependency problem.

@patcon

This comment has been minimized.

patcon commented Sep 30, 2015

bump. Any update on v2 of the cookbook?

@martinisoft

This comment has been minimized.

Member

martinisoft commented Jan 8, 2016

@patcon For the update I think we'll look at merging either #28 or #29 to get this shipped before we look at a 2.0 release. Sorry about the long wait on an answer here.

@weppos

This comment has been minimized.

Member

weppos commented Jan 8, 2016

@martinisoft I see both #28 and #29 are focused on using Fog. I suggest we should switch to our Ruby client, as it is definitely more flexible than Fog. Moreover, we have better control over the release cycle.

That will be increasingly more important once we'll release API v2.

@martinisoft

This comment has been minimized.

Member

martinisoft commented Jan 8, 2016

@weppos That is a fair point. I'll look at whipping up a pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment