Skip to content

"Admin" panel for the official registry API #182

Closed

Description

@tadasant

We need to work out the scope and "who would have this permission" type of questions, but in general I believe there will be some need for an escape hatch of this nature for a while. e.g. in the case of some spam attack, malicious attack, or even just an edge case bug that gets our data into a bad state. It would be good to have something simple in place here so we don't have to make direct changes to infra via privileged access to e.g. a Postgres database.

Activity

  1. domdomegg commented on Aug 26, 2025

    @domdomegg
    Member

    As part of this issue we should add docs on how to use this API to takedown a malicious server, with an easy to follow runbook for maintainers to follow.

  2. self-assigned this
    on Aug 26, 2025
  3. added a commit that references this issue on Aug 28, 2025
    8afe162
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

go-live blockerThis issue is one we need to address prior to initial go-liveimplementation workShovel-ready to write code

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions