[Documentation] Guide KB still references decommissioned QDS_ADMIN role (follow-up to incident#253) #10
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Guide KB still documents
QDS_ADMINafter the code purge (stale docs)Follow-up to hiveops-incident#253 (Remove decommissioned QDS_ADMIN role from 5 backends), which is done and merged —
QDS_ADMINis now gone from theSecurityConfig/InstitutionContextof hiveops-incident, hiveops-recon, hiveops-devices, hiveops-guide, hiveops-transactions ondevelop, and it was already removed from the hiveops-authRoleenum (972a28a) so no JWT can carry it.#253 deliberately scoped out the Guide's knowledge-base content. As a result the Guide now describes role-gates that no longer exist in code — e.g. several modules quote
hasAnyRole('USER','CUSTOMER','ADMIN','MSP_ADMIN','QDS_ADMIN','BCOS_ADMIN')verbatim, but the realSecurityConfigno longer listsQDS_ADMIN. Doc-accuracy defect, not a runtime issue.Scope — strip
QDS_ADMINfrom Guide content (26 refs / 23 files)Remove
QDS_ADMINfrom role/allow-list mentions; keep the surviving roles (USER, CUSTOMER, ADMIN, MSP_ADMIN, BCOS_ADMIN, plusAGENT/SYSTEMwhere relevant) exactly as-is.Also (separate repo, minor)
hiveops-src/SECURITY_AUDIT_2026-05-08.md— theQDS_ADMINrow was reworded to "legacy, pending purge"; now that the purge is complete it could read "removed (decommissioned)". Dated audit doc, low priority.Notes
hiveops-guide/scripts/coverage-reconcile.pystill passes after edits.develop, PR ->develop.