[OpenSpec] cmdb-import-mapping-view #1301

⚠️ OpenSpec-managed issue — this content is automatically synced
from the openspec/ directory. Manual edits will be overwritten on next sync.

Artifacts

• ✅ Metadata
• ✅ Proposal
• ✅ Specs
• ✅ Design
• ✅ Tasks
• 🔲 Plan
• 🔲 Review

Summary

A Nextcloud administrator can view and edit the column mapping of the CMDB import in OpenRegister. The four sheet packs of the import (module, manufacturer, usage and business owner) move into OpenRegister's existing migration-pack store, where OpenRegister's pack editor shows and changes them. The import reads each pack from that store first and runs exactly what the administrator saved. The packs that ship under lib/Settings/cmdb-import/ become the seed and the fallback: a repair step stores them in OpenRegister as built-in packs, and replaces a stored pack nobody edited when a later release ships a newer one. An edited pack is never overwritten. A stored pack that is invalid, or that breaks a rule of the import, stops the import with 503 MAPPING_UNAVAILABLE naming the pack; it never falls back to the files silently. GET /api/settings/cmdb-import/mapping says per pack where it comes from, which versions are stored and shipped, whether it was edited, and links to its editor in OpenRegister. Showing that per pack in the "CMDB import" section of stackiq's admin settings is the frontend part (#1289).

Specs

• 📄 cmdb-export-import

Tasks

• Implement
• Test
• Implement
• Test
• Implement
• Test
• Implement
• Test
• Implement (backend strings, the section's strings and documentation)
• Test
• Implement
• Test
• Implement
• Test
• Implement
• Test

Design

See design.md for technical design details.

Synced from openspec/changes/cmdb-import-mapping-view by OpenSpec workflow
App: stackiq