Skip to content

discovery(authz): FOURTH scope enum — api/schemas_system.py SecretScope (CHAT/GENERAL legacy) + plain-class copy in infra secrets_manager.py #11759

Closed

Description

@mrveiss

From #11290 implementation: api/schemas_system.py:3300 defines another SecretScope (CHAT/GENERAL — legacy Redis chat-secrets store, iterated in the /scopes API response) and autobot-infrastructure/shared/scripts/secrets_manager.py:60 carries a plain-class copy. Outside #11290's three-enum scope but same canonical-debt class: fold or rename to distinct names to avoid the same collision pattern #6828 had.

Activity

  1. github-actions commented on Jul 15, 2026

    @github-actions
    Contributor

    PR #11765 (merged to Dev_new_gui) references this issue with a close keyword.

    refactor(authz): rename legacy chat-secrets scope enum — resolve SecretScope name collision (#11759)

    If this issue is fully resolved, close it manually. If work remains, no action is needed.

  2. mrveiss commented on Jul 15, 2026

    @mrveiss
    OwnerAuthor

    Closed — merged to Dev_new_gui. Commit: 6348d5f (PR #11765). Legacy chat-secrets enum renamed ChatSecretScope (members/values untouched; /api/secrets/types payload pinned by new test, base-vs-new IDENTICAL); consumers audited zero cross-contamination; infra script import-rot fixed in-scope; siblings tracked in #11761.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions