mirror of
https://github.com/Stirling-Tools/Stirling-PDF.git
synced 2026-09-03 05:10:16 +03:00
Anthony Stirling
547dce4cf3
# Description of Changes - The multi-node compose stack + behave suite (11 features) - The nightly multinode-e2e job in build-enterprise.yml cuke features are cluster_health - both nodes boot healthy and join the Valkey backplane load_balancing - traffic spreads across nodes; no spurious 401 when bounced cross_node_auth - a token from one node validates on all nodes (shared DB keys) shared_state - teams/sources/org visible from every node policy_management - create/rename/delete a policy on any node, reflected everywhere source_management - source CRUD cross-node; referenced source can't be deleted anywhere connections - S3 connection resolves (secret masked) and deletes cluster-wide processor_ledger - files processed exactly once even when both nodes trigger together policy_run_coordination - a run on one node is visible from every node rate_limiting - rate-limit counters shared via Valkey, not per node failover - LB keeps serving when a node dies; recovered node accepts existing tokens can now start a full node system with export PREMIUM_KEY=<your licence key> ./start-multinode-test.sh starts a 40 person org DB install with multi node and database (--no-seed to have without DB on startup) 4 teams 1 s3 connection 1 policy --- ## Checklist ### General - [ ] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [ ] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [ ] I have performed a self-review of my own code - [ ] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [ ] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [ ] I have run `task check` to verify linters, typechecks, and tests pass - [ ] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#7-testing) for more details.
26 lines
1.4 KiB
Gherkin
26 lines
1.4 KiB
Gherkin
@multinode @sources
|
|
Feature: Source management across nodes
|
|
|
|
Sources are durable state. A source created on one node must be usable from
|
|
every node, and the guard that stops a referenced source from being deleted
|
|
must hold across nodes - even when the source and the referencing policy were
|
|
created on different nodes.
|
|
|
|
Scenario: A source created on one node is visible and deletable from the other
|
|
Given the multi-node stack is running
|
|
And I am logged in as admin
|
|
When I create an S3 source named "regr_src_alpha" on node "1"
|
|
Then the source "regr_src_alpha" should be visible from every node
|
|
When I delete the source "regr_src_alpha" on node "2"
|
|
Then the source "regr_src_alpha" should be absent from every node
|
|
|
|
Scenario: A referenced source cannot be deleted from another node
|
|
Given the multi-node stack is running
|
|
And I am logged in as admin
|
|
When I create an S3 source named "regr_src_ref" on node "1"
|
|
And I create a policy named "regr_pol_ref" referencing source "regr_src_ref" via the load balancer
|
|
Then deleting the source "regr_src_ref" from node "2" is rejected because it is referenced
|
|
When I delete the policy "regr_pol_ref" on node "2"
|
|
And I delete the source "regr_src_ref" on node "1"
|
|
Then the source "regr_src_ref" should be absent from every node
|