Added support for authentication tokens + fix for #1 #2

Ghost · 2019-08-30T14:06:25Z

Ghost komentēja

2019-08-30 14:06:25 +00:00

Pirmreizējs līdzradītājs

I want to use this package, but I am working at a place where I can't be given access to the account's API access token, due to its sheer power over the CloudFlare account.

I can however be granted limited tokens. Due to CloudFlare limitations, there needs to be two tokens - one for listing the domains (and getting the Zone ID that way), and a second one to actually perform the challenges.

This PR implements it. Since I haven't actually tested this "for real" yet, I wanted to at least pass the dry tun tests... so I ended up fixing #1 as well.

EDIT: And I also added and now enforced "standard" via "husky", since it appears to be the style that this project follows.

I want to use this package, but I am working at a place where I can't be given access to the account's API access token, due to its sheer power over the CloudFlare account. I can however be granted limited tokens. Due to CloudFlare limitations, there needs to be two tokens - one for listing the domains (and getting the Zone ID that way), and a second one to actually perform the challenges. This PR implements it. Since I haven't actually tested this "for real" yet, I wanted to at least pass the dry tun tests... so I ended up fixing #1 as well. EDIT: And I also added and now enforced "standard" via "husky", since it appears to be the style that this project follows.

Izmaiņu pieprasījums ir bojāts, jo dzēsta informācija no atdalītā repozitorija.

Nepieciešams pieteikties, lai pievienotos šai sarunai.

1 dalībnieki

Paziņojumi

Izpildes termiņš

Izpildes termiņš nav uzstādīts.

Atkarības

Nav atkarību.

Atsaucas uz: coolaj86/acme-dns-01-cloudflare.js#2