provider/ovh: new provider, resource ovh_domain_zone

[remijouannet]

Hi,

after the pull request of @yanndegat i recreate my pull request to add this ressource to ovh provider

i'v written that simple plugin https://github.com/remijouannet/terraform-provider-ovh
with only one resource just to manipulate OVH domains,
so my PR include only one resource

however I don't know if the acceptance tests i wrote are enough or not,
i didn't write the terraform documentation yet as i don't know if my PR require more work or not

here is a little README:
howto

if you want to use the OVH API you have to generate:

An Application Key
An Application Secret Key
A Consumer Key

you can generate all three on this page
https://eu.api.ovh.com/createToken/

the following rights are needed for this plugin

GET : /domain/zone/*
PUT : /domain/zone/*
POST : /domain/zone/*
DELETE : /domain/zone/*
GET : /me

ovh.tf example

provider "ovh" {
application_key = "azrzqrgqvvdsfgsfffgc"
application_secret = "aztfqsqfsdcsdqezrfdvcx"
consumer_key = "aergfvdsrgtfbvcretfgd"
}

resource "ovh_domain_zone_record" "test" {
zone = "testdemo.ovh"
subDomain = "test"
fieldType = "A"
ttl = "3600"
target = "0.0.0.0"
}

testacc

export OVH_APPLICATION_KEY="arqzergfazfeef"
export OVH_APPLICATION_SECRET="aertedytfghftyhytghbgfv"
export OVH_CONSUMER_KEY="tyfghjhuyghvbjhuytghbjygh"
export OVH_ZONE="testdemo.ovh"

then use the makefile : make testacc TEST=./builtin/providers/ovh

[stack72]

Hi @remijouannet

Thanks for the work here - please can you enhance the PR with some documentation as well?

Thanks

Paul

[remijouannet]

Hi,
done, is that enough ?

[stack72]

@yanndegat thoughts on this PR would be awesome :)

[yanndegat]

hi @stack72. will do
hi @remijouannet could you rebase your PR on the new https://github.com/terraform-providers/terraform-provider-ovh/ project please ?
and we'll start the review from there.

[stack72]

Closed as was moved to https://github.com/terraform-providers/terraform-provider-ovh/issues/3

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.