You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
Closes [MPT-18141](https://softwareone.atlassian.net/browse/MPT-18141)
- Rename CLI option `--fake` to `--manual` in the migrate command
- Rename `FakeCommand` class to `ManualCommand` throughout the codebase
- Update migration status enum member from `FAKE_APPLY` to
`MANUAL_APPLIED` with value changed from `"faked"` to `"manual"`
- Rename `Migration.fake()` method to `Migration.manual()` and update
semantics to set `applied_at` timestamp while clearing `started_at`
- Update command factory to route manual migrations through
`ManualCommand`
- Update all error messages and status labels from "fake mode" to
"manual mode"
- Update documentation to reflect manual mode terminology
- Rename and update test cases to use `--manual` flag and verify manual
mode behavior
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
[MPT-18141]:
https://softwareone.atlassian.net/browse/MPT-18141?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
| running | `started_at` is set and `applied_at` is empty |
275
275
| failed | `started_at` and `applied_at` are empty for an existing state |
276
-
| faked | `started_at` is empty and `applied_at` is set |
276
+
| manual | `started_at` is empty and `applied_at` is set |
277
277
| applied | Both `started_at` and `applied_at` are set |
278
278
| not applied | No state entry exists for the migration file |
279
279
@@ -321,7 +321,7 @@ Run `mpt-service-cli --help` to see all available commands and params:
321
321
**Migration fails to run:**
322
322
- Review the error message in the terminal output
323
323
- Check your `Migration.run()` implementation for syntax errors
324
-
- Fix the issue and re-run the migration or use `--fake` to mark it as applied
324
+
- Fix the issue and re-run the migration or use `--manual` to mark it as applied
325
325
326
326
**NOTE:** There is currently no automatic rollback mechanism. If a migration partially modifies data before failing, you must manually revert those changes or create a new migration to fix the state.
0 commit comments