Account requires deprecated field `defaultNameservers`

[dinesen-blinq]

Describe what happened

When creating or updating an Account, it will fail unless the deprecated field default_nameservers is provided.

I am using @pulumi/cloudflare: ^6.2.0.

Sample program

new cloudflare.Account(
  'account',
  {
    name: `Main Account`,
    settings: {
      // defaultNameservers: 'custom.account',
    },
  },
);

Log output

    error: failed to make http request: PUT "https://api.cloudflare.com/client/v4/accounts/<redacted>": 400 Bad Request {"success":false,"errors":[{"code":1001,"message":"Unknown setting 'default_nameservers' for account."}],"messages":[],"result":null}

Affected Resource(s)

No response

Output of pulumi about

pulumi about
CLI          
Version      3.173.0
Go Version   go1.24.3
Go Compiler  gc

Plugins
KIND      NAME        VERSION
resource  cloudflare  6.2.0
language  nodejs      3.173.0

Host     
OS       darwin
Version  15.5
Arch     arm64
...

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[t0yv0]

Thanks for filing this up!

I've tried reproducing on something like this:

import * as pulumi from "@pulumi/pulumi";
import * as cloudflare from "@pulumi/cloudflare";

new cloudflare.Account(
  'account',
  {
    type: 'standard',
    name: `Main Account`,
    settings: {
      // defaultNameservers: 'custom.account',
    },
  },
);

Preview succeeds but I was not able to verify pulumi up yet because our test account is not yet setup to manage/create accounts.

That said something peculiar is happening:

{
  "method": "/pulumirpc.ResourceProvider/Create",
  "request": {
    "urn": "urn:pulumi:dev::cloudflare-1226::cloudflare:index/account:Account::account",
    "properties": {
      "name": "Main Account",
      "settings": {},
      "type": "standard"
    },
    "preview": true,
    "name": "account",
    "type": "cloudflare:index/account:Account"
  },
  "response": {
    "properties": {
      "createdOn": "04da6b54-80e4-46f7-96ec-b56ff0331ba9",
      "id": "04da6b54-80e4-46f7-96ec-b56ff0331ba9",
      "name": "Main Account",
      "settings": {
        "defaultNameservers": "cloudflare.standard",
        "enforceTwofactor": false,
        "useAccountCustomNsByDefault": false
      },
      "type": "standard"
    }
  },
  "metadata": {
    "kind": "resource",
    "mode": "client",
    "name": "cloudflare"
  }
}

The default got applied as "defaultNameservers": "cloudflare.standard", coming from here:

https://github.com/cloudflare/terraform-provider-cloudflare/blob/72a74193561eaaf004a9aa21499c44ca729e8bd3/internal/services/account/schema.go#L75

And this field is being modeled in https://github.com/cloudflare/terraform-provider-cloudflare/blob/72a74193561eaaf004a9aa21499c44ca729e8bd3/internal/services/account/model.go#L39 still, which does participate in sending the JSON data: https://github.com/cloudflare/terraform-provider-cloudflare/blob/72a74193561eaaf004a9aa21499c44ca729e8bd3/internal/services/account/resource.go#L67

If the Cloudflare API no longer supports receiving this data, removing it from the model might do the trick. I am curious if this issue reproduces in plain Terraform, in which case we can open an issue upstream and fix it there; if it does not reproduce in Terraform, there must be a discrepancy in how defaults are applied between Terraform and Pulumi in this case, which is something we should fix in pulumi-terraform-bridge.

Would you be able to verify if this or similar program provisions fine under Terraform? Thank you.

resource "cloudflare_account" "my-account" {
    type = "standard"
    name = "Main Account"
)

[dinesen-blinq]

Thanks for investigating.

I have not been able to reproduce with Terraform yet, but have some more information.

Regardless of setting defaultNameservers, it fails. In short - I don't think it is possible to update a cloudflare.Account.

[t0yv0]

That's not great, sorry to hear! If there is no workaround and you cannot use cloudflare.Accountwe can try a few things such as patching out Default NameServers from the Go definition. Could you help verify if this holds in Terraform, and also if it holds with terraform -refresh=false, this would be greatly appreciated. If it does not repro in Terraform and you have no workaround to use cloudflare.Account I can escalate this.