Skip to content

[LIBCLOUD-745] Add Vultr DNS provider implementation - #579

Closed
aleGpereira wants to merge 1 commit into
apache:trunkfrom
aleGpereira:LIBCLOUD-745_vultr_provider
Closed

[LIBCLOUD-745] Add Vultr DNS provider implementation#579
aleGpereira wants to merge 1 commit into
apache:trunkfrom
aleGpereira:LIBCLOUD-745_vultr_provider

Conversation

@aleGpereira

Copy link
Copy Markdown
Contributor

I have another provider to add. Thanks for your awesome work guys.

@aleGpereira
aleGpereira force-pushed the LIBCLOUD-745_vultr_provider branch 2 times, most recently from b0060a1 to 0382755 Compare September 25, 2015 17:11
@aleGpereira
aleGpereira force-pushed the LIBCLOUD-745_vultr_provider branch from 0382755 to cd2684f Compare September 25, 2015 17:49

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not a good idea to default to mutable types (dicts, lists), I will change it to default to None and do extra = extra or {} inside the method body when merging the PR.

@Kami

Kami commented Sep 25, 2015

Copy link
Copy Markdown
Member

Thanks for syncing the branch with latest trunk :)

@asfgit asfgit closed this in fd5827a Sep 25, 2015
@Kami

Kami commented Sep 25, 2015

Copy link
Copy Markdown
Member

Fixed minor Python 3 compatibility issue and merged patch into trunk. Thanks!

@aleGpereira
aleGpereira deleted the LIBCLOUD-745_vultr_provider branch October 12, 2015 15:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants