Bluecat provider " is not a valid deployment type"

[zigsphere]

What happened:

When updating to version 0.12.2 from 0.10.1, if the dnsDeployType is not set in the BlueCat configuration file, then the container fails with: {"level":"fatal","msg":" is not a valid deployment type","time":"2022-08-11T17:38:48Z"}. According to the documentation, this is an optional field.

If I do specify the field, I still continue to get the " is not a valid deployment type" error regardless.

What you expected to happen: Container to function as expected without having to specify the dnsDeployType in the Bluecat configuration file.

How to reproduce it (as minimally and precisely as possible): Deploy external-dns with version 0.12.2 with the Bluecat provider and omitting the dnsDeployType parameter in the Bluecat.json configuration file. This also occurs if you specify dnsDeployType.

Anything else we need to know?:

Environment:

• External-DNS version (use external-dns --version): 0.12.2
• DNS provider: Bluecat
• Others: None

Example bluecat.json config:

{
  "gatewayHost": "https://foo.internal",
  "gatewayUsername": "svc-bar",
  "gatewayPassword": "astrongpassword",
  "dnsConfiguration": "Foobar",
  "dnsView": "prod",
  "rootZone": "internal",
  "skipTLSVerify": false
}

Also tried:

{
  "gatewayHost": "https://foo.internal",
  "gatewayUsername": "svc-bar",
  "gatewayPassword": "astrongpassword",
  "dnsConfiguration": "Foobar",
  "dnsView": "prod",
  "rootZone": "internal",
  "dnsDeployType": "full-deploy",  <--- ADD THIS
  "skipTLSVerify": false
}

But continued to receive " is not a valid deployment type" when the pod started, resulting in a CrashLoopBackOff.