DB Update Causes error on Cron

@johnpicozzi: I also get this error message after update from 8.x-1.0-beta2 to 8.x-1.0-beta3 and first I thought it has something to do with my custom purge Queuer plugin.

For me it was resolved after I re-edit on deployed PROD env my Drupal cloudflare settings under /admin/config/services/cloudflare which finally updated Cloudflare zone config in this 2 steps config form. Maybe update hook handles this a little bit in a wrong way?

Hi I have encountered the same issue on this version of Cloudflare as well. I am unable to modify the config values on the prod site to get these errors gone. I've created a patch that can be used to allow you to edit the Cloudflare admin config form which will let you enable a Zone & bypass these errors. It seems the root issue does stem from the drush DB updates after updating to this version. This is a workaround for those who need to get past these errors but the root issue should probably still be looked into. The MR in comment #6 should do the trick.

Since posting this I have updated to Drupal 10.2 and I'm using the 2.0.0 Alpha 1 Version of the module. I'm still seeing this error when running cron in my logs. I think the MR needs to be reviewed to work with this version of the module. Also based on the comment above it seems the root cause still needs to be investigated.

Updating this to Version 2.0.0 Alpha 1.

Stilling having this issue on beta1- upping the version. The patches above don't apply cleanly.

@johnpicozzi: Could you please double check structure of your current cloudflare.settings.yml and which version of purge module you are using in your project.

client_ip_restore_enabled: true
remote_addr_validate: true
bypass_host: ...
valid_credentials: true
zone_id:
  <ZONE_ID>: <ZONE_ID>
zone_name: ''
auth_using: key
api_token: ''
apikey: ...
email: ...

For me it looks like this and I don't get any error.

@it-cru Thanks for the assist here. After looking at my cloudflare.settings.yml and comparing with yours I noticed a difference. After re-saving my Cloudflare settings the issues has gone away. I'm moving this to closed (outdated) as I think this has been resolved.