Follow-on to the trucking new-carrier slug fix: - success page: add dot-new-carrier-bundle to DOT_SLUGS + NEW_CARRIER_SLUGS so the order-confirmation 'what to expect' messaging classifies it as trucking. - pipeline_orchestrator: the trucking onboarding PIPELINE was keyed under the bare 'new-carrier-bundle' slug, which is the TELECOM bundle's slug (also a collision at the worker layer). Re-keyed to 'dot-new-carrier-bundle' so a trucking bundle never runs the telecom pipeline (and vice versa). |
||
|---|---|---|
| .. | ||
| canada-crtc | ||
| cancel | ||
| cancelled | ||
| crypto-pay | ||
| dot-compliance | ||
| fcc-499a | ||
| fcc-499q | ||
| fcc-carrier-registration | ||
| fcc-compliance | ||
| formation | ||
| identity-complete | ||
| neca-ocn | ||
| state-puc | ||
| success | ||
| trucking-new-carrier | ||