eject-and-customize

When UMES extensions cannot satisfy your customization needs, you can eject the core pricing logic module into your source tree. This creates a local, version-controlled copy for safe modification while preserving upgrade paths.

Ejecting a core module involves copying the target module into your source tree, re-registering it, and preparing it for customization. This workflow requires a risk assessment, documentation, and a tracked customization log.

You should eject core modules only as a last resort when UMES extensions cannot expose the required changes. This applies to scenarios needing modifications to authentication flows, pricing logic, or core workflows.

Ejecting core modules does not inherently break upgrades, but it introduces a maintenance burden. The process includes safe modification zones and upgrade strategies to minimize conflicts and help merge upstream changes.

The main limitation is the ongoing maintenance burden, as you must manually merge upstream changes to keep the customized module updated. You must also maintain strict documentation and a tracked customization log to manage risk.

Yes, you can modify authentication flows by ejecting the core module when extensions do not expose the necessary logic. This creates a local copy in your source tree that you can version-control and customize safely.