issue-7-config-cleanup-legacy-removal #18

Merged
parkel merged 7 commits from issue-7-config-cleanup-legacy-removal into master 2026-05-21 02:57:39 +02:00
Owner

Summary

  • Retires public short aliases for configuration commands so Django remains the primary operating surface.
  • Removes the old YAML import/export path and requires an explicit Django config source for backup and retention engine calls.
  • Removes obsolete GlobalConfig storage fields: pobsync_home and data.
  • Normalizes runtime/admin/help labels around state root, backup root, schedule expression, and Django-managed configuration.
  • Keeps useful maintainer commands available through pobsync django ... for automation and debugging.
  • Cleans up operator-facing errors so they no longer leak model names like HostConfig or GlobalConfig.

Tests

  • docker compose build web
  • docker compose run --rm web python manage.py test pobsync_backend -v 2

Closes #7

## Summary - Retires public short aliases for configuration commands so Django remains the primary operating surface. - Removes the old YAML import/export path and requires an explicit Django config source for backup and retention engine calls. - Removes obsolete `GlobalConfig` storage fields: `pobsync_home` and `data`. - Normalizes runtime/admin/help labels around state root, backup root, schedule expression, and Django-managed configuration. - Keeps useful maintainer commands available through `pobsync django ...` for automation and debugging. - Cleans up operator-facing errors so they no longer leak model names like `HostConfig` or `GlobalConfig`. ## Tests - `docker compose build web` - `docker compose run --rm web python manage.py test pobsync_backend -v 2` Closes #7
parkel added 7 commits 2026-05-21 02:57:32 +02:00
Remove the short pobsync aliases for global config, host config, and
schedule changes so the public CLI no longer points operators toward the
old configuration workflow.

Keep operational aliases for backup, discovery, retention, worker, and
scheduler debugging, and document explicit Django management commands for
automation use.
Hide the old pobsync_home field from the Django admin and replace legacy
operator-facing labels with runtime state root and backup root terminology.

Rename admin compatibility fieldsets, update self-check/config-check text,
and refresh management command help so Django/systemd stays the primary
mental model.
Drop the pre-Django YAML import/export management commands and remove the
file-based config loader fallback from the backup and retention engines.

Keep the runtime config bridge backed by Django models, and add tests that
ensure engine operations require an explicit Django config source.
Drop the obsolete pobsync_home field from GlobalConfig and remove it from
runtime config generation, form saves, and configuration commands.

The runtime state root now comes exclusively from POBSYNC_HOME/settings,
which keeps the Django model focused on backup behavior instead of install
layout.
Drop the unused GlobalConfig.data field and remove the remaining YAML
config path helpers from PobsyncPaths.

Keep HostConfig.config as runtime state for preflight data, and relabel it
in the admin so it no longer reads as legacy compatibility storage.
Prefer --schedule-expression for scripted schedule updates while keeping
--cron as a compatibility alias.

Clean up management command help, errors, and output so operator-facing
text talks about hosts, global config, and Django backup configuration
instead of model names or old SQL-backed pobsync wording.
Replace remaining model-name based configuration errors with labels that
match the Django-first operating model.

Add coverage for missing global config and host configuration errors so
operator-facing messages stay readable.
parkel merged commit 362a9dde62 into master 2026-05-21 02:57:39 +02:00
parkel deleted branch issue-7-config-cleanup-legacy-removal 2026-05-21 02:57:39 +02:00
Sign in to join this conversation.