[Bug] Repair missing Function mappings table in already-baselined installations #20

New Issue

2026-09-07T12:57:11+02:00

zemion commented

2026-09-07 12:57:11 +02:00

User-reported Function mappings failures were traced to an existing installation whose Access baseline was recorded but whose access_external_function_role_assignments table was missing.

Implemented locally (not committed/pushed): additive forward repair d8f1b4e7a0c3 for release and dev migration tracks. Creates only the missing table with indexes, uniqueness and foreign keys; existing mappings are untouched. Downgrade does not drop retained mappings. Owning EN/DE module documentation and operator guidance updated.

Verification: four isolated migration/API tests cover both tracks, existing-data preservation, repeated upgrades, constraints, cross-tenant rejection and permission denial. Both live list and delta endpoints now return HTTP 200; administration page loads without API errors.

Operational note: the existing development autoreloader applied the additive migration when the new files appeared, before the planned manual migration/backup step. No manual broad upgrade or seed/reset was performed. A post-repair PostgreSQL backup was verified; it is not a pre-repair restore point.

Keep this issue open until these local changes are published. No issue closure or release claim yet.

User-reported Function mappings failures were traced to an existing installation whose Access baseline was recorded but whose `access_external_function_role_assignments` table was missing. Implemented locally (not committed/pushed): additive forward repair `d8f1b4e7a0c3` for release and dev migration tracks. Creates only the missing table with indexes, uniqueness and foreign keys; existing mappings are untouched. Downgrade does not drop retained mappings. Owning EN/DE module documentation and operator guidance updated. Verification: four isolated migration/API tests cover both tracks, existing-data preservation, repeated upgrades, constraints, cross-tenant rejection and permission denial. Both live list and delta endpoints now return HTTP 200; administration page loads without API errors. Operational note: the existing development autoreloader applied the additive migration when the new files appeared, before the planned manual migration/backup step. No manual broad upgrade or seed/reset was performed. A post-repair PostgreSQL backup was verified; it is not a pre-repair restore point. Keep this issue open until these local changes are published. No issue closure or release claim yet.

zemion commented

2026-09-08 05:23:52 +02:00

Reconciled 2026-09-08: implemented and published

This supersedes the earlier local/unpublished status. The owning fix is on remote main and the verified v0.1.25 tag (commit 8f8072b4aeb5), included in the published 0.1.45 source/package composition.

Both release and dev migration tracks contain additive repair d8f1b4e7a0c3; four isolated migration/API tests verify missing-table repair, repeated upgrades, retained mappings/constraints and authorization. EN/DE manifest guidance and EXTERNAL_FUNCTION_MAPPING_SCHEMA_REPAIR.md are included. The earlier operational note remains valid: the development autoreloader applied the repair, and the recorded backup is post-repair, not a pre-repair restore point. No migration or live DB change was performed by this reconciliation.

The completed, unmodified release tools/checks/check-focused.sh run passed, including 213 browser conformance cases and the relevant backend suites. The audit matched current remote branches/tags and reviewed the original acceptance criteria and subsequent comments. Closing the implemented source/package scope. This is not a runtime deployment claim: Meta #52 and website #9 retain their independent runtime/public-site holds. No tag was moved.

## Reconciled 2026-09-08: implemented and published This supersedes the earlier local/unpublished status. The owning fix is on remote `main` and the verified [`v0.1.25` tag](https://git.add-ideas.de/GovOPlaN/govoplan-access/src/tag/v0.1.25) ([commit `8f8072b4aeb5`](https://git.add-ideas.de/GovOPlaN/govoplan-access/commit/8f8072b4aeb50be6c3b9c1f5943604c305be81e0)), included in the published [0.1.45 source/package composition](https://git.add-ideas.de/GovOPlaN/govoplan/src/commit/88b685ff5e689acf096bdfc7084bd108e801e86e/docs/releases/0.1.45.md). Both release and dev migration tracks contain additive repair `d8f1b4e7a0c3`; four isolated migration/API tests verify missing-table repair, repeated upgrades, retained mappings/constraints and authorization. EN/DE manifest guidance and `EXTERNAL_FUNCTION_MAPPING_SCHEMA_REPAIR.md` are included. The earlier operational note remains valid: the development autoreloader applied the repair, and the recorded backup is post-repair, not a pre-repair restore point. No migration or live DB change was performed by this reconciliation. The completed, unmodified release `tools/checks/check-focused.sh` run passed, including 213 browser conformance cases and the relevant backend suites. The audit matched current remote branches/tags and reviewed the original acceptance criteria and subsequent comments. Closing the implemented source/package scope. This is not a runtime deployment claim: [Meta #52](https://git.add-ideas.de/GovOPlaN/govoplan/issues/52) and [website #9](https://git.add-ideas.de/add-ideas/addideas-govoplan-website/issues/9) retain their independent runtime/public-site holds. No tag was moved.

zemion closed this issue

2026-09-08 05:23:52 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-access#20