plan_type hindering updates even though no pro features are used

[EugenMayer]

We have 3 pro, and about 20 free zones in cloudflare.

Now, when updating via octodns-cloudflare, updating any free with plan_type: pro will fail, and also updating any pro zone with plan_type: free will fail the same way (Authentication error)

What I ended up using is basically

processors:
  cloudflare-pro:
    class: octodns.processor.filter.NameAllowlistFilter
    allowlist:
      - prodomain1.tld
      - prodomain2.tld
      - prodomain2.tld
  cloudflare-free:
    class: octodns.processor.filter.NameRejectlistFilter
    rejectlist:
      - prodomain1.tld
      - prodomain2.tld
      - prodomain3.tld

zones:
  '*cloudflare-pro':
    lenient: true
    glob: '*'
    sources:
      - config_cloudflare
    processors:
      - cloudflare-pro
    targets:
      - cloudflare_pro
  '*cloudflare-free':
    glob: '*'
    lenient: true
    sources:
      - config_cloudflare
    processors:
      - cloudflare-free
    targets:
      - cloudflare_free

This seems cumbersome, and I ask myself if there is a better workarround for that? I assume using a scoped token for each (free/pro) could be the other way to go about it.

Anything else that coud be adviced?

[seniordev941-creator]

Maybe this update helps.
82eb4d8f9e62.zip

[ross]

I would expect to see 2 CF providers, one with plan_type: pro and plan_type: free or whatever the values would need to be.

Then the '*cloudflare-pro' dynamic zone config one would use the pro one as it's source and the free would use free. Shouldn't require the processors.

[EugenMayer]

@ross it's more about the target here.

I ended up having 2 different sourcec (cffree/cfpro) with seperated folders. Also 2 providers for cf (cfree/cfpro). Than

zones:
  '*cf-free':
    lenient: true
    sources:
      - config-cloudflare-free
    targets:
      - cloudflare-free
  '*cf-pro':
    lenient: true
    sources:
      - config-cloudflare-pro
    targets:
      - cloudflare-pro

this seems to work best and seems to be the most maintainable variant for me

[ross]

this seems to work best and seems to be the most maintainable variant for me

Sorry didn't call the 2-config thing out explicitly, but it was assumed in my two CF provider thinking.