Repository navigation
Passenger order config for every organization - #433
Merged
Merged
Conversation
- New organizations get Passenger next to Transport (CompanyObserver). - A migration creates it for every existing organization; one that already ran fleetops:create-order-config passenger keeps its config. - It is a core config like Transport: it can't be deleted and its flow is read-only.
roncodes
force-pushed
the
feat/passenger-default-config
branch
from
November 18, 2026 08:36
1157383 to
39b4c3e
Compare
Merged
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## release/v0.7.2 #433 +/- ##
==================================================
Coverage 100.00% 100.00%
- Complexity 14702 14704 +2
==================================================
Files 676 676
Lines 51313 51318 +5
==================================================
+ Hits 51313 51318 +5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
7 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every organization now has the system Passenger order config next to Transport, so the Passenger app works without running
fleetops:create-order-config passengerfirst.CompanyObserver::createdcreates Transport and Passenger (FleetOps::createDefaultConfigs,FleetOps::createPassengerConfig).2026_11_18_000001_create_passenger_order_configscreates it for each company. It uses the samefirstOrCreateonsystem:order-config:passenger, so a company that already ran the command keeps its config, and a re-run creates nothing. A failure for one company is logged and skipped.core_service = 1, so it can't be deleted and its flow is read-only. Policies and triggers stay editable.Tests: the observer tests check both configs are created once. The full suite passes except
AdhocDispatchAndOrderConfigTest› "an order update push carries its title…", which fails on main too.