_PROVIDER flag phase 1: generate warnings

docs/_providers/activedir.md

@@ -30,6 +30,7 @@ The `ActiveDirectory_PS` provider reads an `ADServer` setting from `creds.json`
 ```js
 {
   "activedir": {
+    "_PROVIDER": "ACTIVEDIRECTORY_PS",
     "ADServer": "ny-dc01"
   }
 }
@@ -41,6 +42,7 @@ If you want to modify the "fake powershell" mode details, you can set them in th
 ```js
 {
   "activedir": {
+    "_PROVIDER": "ACTIVEDIRECTORY_PS",
     "ADServer": "ny-dc01",
     "fakeps": "true",
     "pslog": "powershell.log",
@@ -49,6 +51,7 @@ If you want to modify the "fake powershell" mode details, you can set them in th
 }
 ```
 
+{% include providerfield.html %}
 
 An example DNS configuration:
 

docs/_providers/akamaiedgedns.md

@@ -28,6 +28,7 @@ In the credentials file (creds.json), you must provide the following:
 
 ```json
 "akamaiedgedns": {
+    "_PROVIDER": "AKAMAIEDGEDNS",
     "client_secret": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
     "host": "akaa-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.xxxx.akamaiapis.net",
     "access_token": "akaa-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",

docs/_providers/autodns.md

@@ -14,6 +14,7 @@ In your credentials file, you must provide [username, password and a context](ht
 {% highlight json %}
 {
   "autodns": {
+    "_PROVIDER": "AUTODNS",
     "username": "autodns.service-account@example.com",
     "password": "[***]",
     "context": "33004"

docs/_providers/axfrddns.md

@@ -42,6 +42,7 @@ For instance, your `creds.json` might looks like:
 ```json
 {
     "axfrddns": {
+        "_PROVIDER": "AXFRDDNS",
         "transfer-key": "hmac-sha256:transfer-key-id:Base64EncodedSecret=",
         "update-key": "hmac-sha256:update-key-id:AnotherSecret="
     }

docs/_providers/azuredns.md

@@ -11,6 +11,7 @@ You can specify the API credentials in the credentials json file:
 ```json
 {
  "azuredns_main":{
+      "_PROVIDER": "AZURE_DNS",
       "SubscriptionID": "AZURE_SUBSCRIPTION_ID",
       "ResourceGroup": "AZURE_RESOURCE_GROUP",
       "TenantID": "AZURE_TENANT_ID",
@@ -33,6 +34,7 @@ export AZURE_CLIENT_SECRET=BBBBBBBBB
 ```json
 {
  "azuredns_main":{
+      "_PROVIDER": "AZURE_DNS",
       "SubscriptionID": "$AZURE_SUBSCRIPTION_ID",
       "ResourceGroup": "$AZURE_RESOURCE_GROUP",
       "TenantID": "$AZURE_TENANT_ID",

docs/_providers/bind.md

@@ -18,6 +18,7 @@ you can specify a `directory` where the provider will look for and create zone f
 ```json
 {
   "bind": {
+    "_PROVIDER": "BIND",
     "directory": "myzones",
     "filenameformat": "%U.zone"      << The default
   }

docs/_providers/cloudflare.md

@@ -25,6 +25,7 @@ This method is enabled by setting the "apitoken" value in `creds.json`:
 ```json
 {
   "cloudflare": {
+    "_PROVIDER": "CLOUDFLAREAPI",
     "apitoken": "your-cloudflare-api-token",
     "accountid": "your-cloudflare-account-id"
   }

docs/_providers/cloudns.md

@@ -14,6 +14,7 @@ Current version of provider doesn't support `sub-auth-user`.
 ```json
 {
   "cloudns": {
+    "_PROVIDER": "CLOUDNS",
     "auth-id": "12345",
     "sub-auth-id": "12345",
     "auth-password": "your-password"

docs/_providers/cscglobal.md

@@ -14,6 +14,7 @@ In your `creds.json` file, you must provide your API key and user/client token.
 ```json
 {
   "cscglobal": {
+    "_PROVIDER": "CSCGLOBAL",
     "api-key": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
     "user-token": "yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy",
     "notification_emails": "test@exmaple.tld,hostmaster@example.tld"

docs/_providers/desec.md

@@ -11,6 +11,7 @@ In your providers credentials file you must provide a deSEC account auth token:
 ```json
 {
   "desec": {
+    "_PROVIDER": "DESEC",
     "auth-token": "your-deSEC-auth-token"
   }
 }