Skip to content

Fix/cli commands load config#29

Merged
3m1n3nc3 merged 3 commits into
mainfrom
fix/cli-commands-load-config
Jul 5, 2026
Merged

Fix/cli commands load config#29
3m1n3nc3 merged 3 commits into
mainfrom
fix/cli-commands-load-config

Conversation

@3m1n3nc3

@3m1n3nc3 3m1n3nc3 commented Jul 5, 2026

Copy link
Copy Markdown
Member

No description provided.

3m1n3nc3 added 3 commits July 5, 2026 08:17
Only migrate loaded the project config; the other database-touching commands
read this.app.getConfig('adapter') directly. Under harnesses that hand the
command a fresh CliApp without applying the config (e.g. the Arkstack CLI),
the adapter was undefined — so migrate:fresh silently took the Prisma-schema
path instead of resetting the configured (Kysely) database, i.e. it did not
tear anything down. rollback/seed/models:sync/migrate:history had the same
latent gap.

Each now calls loadArkormConfig() first (idempotent; matches migrate).

migrate:fresh itself is confirmed correct: adapter.resetDatabase() drops all
base tables and enum types in the current schema, then every migration is
re-run from a clean state.

Test: migrate:fresh reaches the adapter reset path when the adapter is only
reachable through arkormx.config (no configureArkormRuntime).
@3m1n3nc3 3m1n3nc3 merged commit fdcc3a2 into main Jul 5, 2026
5 of 6 checks passed
@3m1n3nc3 3m1n3nc3 deleted the fix/cli-commands-load-config branch July 5, 2026 08:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant