cloudflare_compute 1.0.0-alpha4

Manages a queue's HTTP pull consumer (its retry limit and dead-letter queue) as desired state on the queue asset, reconciled to Cloudflare whenever the asset is saved or imported. Requires Drupal 11.2 or later.

Changes since 1.0.0-alpha3

• Issue #3610174: Queue assets have HTTP pull consumer settings: whether the suite reconciles the consumer, its retry limit (max_retries) and its dead-letter queue. Saving the asset (the form, a configuration import, code, or provisioning) creates or updates the consumer to match, keeping its other settings. It never deletes a consumer or replaces a Worker consumer.
• Issue #3610174: $settings['cloudflare']['compute']['reconcile_consumers'] = FALSE turns reconciliation off for an environment that imports another's configuration but does not own its queues. settings.php overrides of a queue asset are honoured.
• Issue #3610174: A status report row shows queues whose last reconcile failed (it does not call Cloudflare), and a new queue detail page shows the desired settings beside the live consumer, with any drift.
• Issue #3610174: A queue list that cannot be read (an unresolvable account, a transport or API error) is reported as that, not as a missing queue. QueueCatalogInterface::findByName() returns error as well (an implementation of the interface must now return it), and an account that cannot be resolved is no longer reported as forbidden.
• Issue #3610174: Upgrading adds the settings to existing queue assets with reconciling off: no Cloudflare call, and existing consumers stay as they are. settings.php overrides are not written into active configuration. Tick "Reconcile this queue's HTTP pull consumer" on a queue to manage it; the form starts from the live consumer's values.
• Issue #3610174: A queue asset now depends on its credential set, so deleting a credential set also deletes the queue assets that use it (their Cloudflare queues are untouched).
• Issue #3610174: Saving the queue form no longer blanks the recorded queue id. This affected all earlier alphas.
• Issue #3610174: Drupal 11.2 or later is now required (^11.2 || ^12).