magus v0.4.3 is out. See what's new
¶ View markdown source · ✎ Suggest an edit
1 min read

MGS9005: token name already exists

magus config mcp connector create or magus config console token create was asked to mint a token under a name the token store already has. Names are unique across the whole store, connectors and console tokens alike, so each is unambiguous to list and revoke.

[MGS9005] magus config mcp connector create: a token named "ci" already
exists; pass a different --name
  see: .../MGS9005.md

Why

A name is the human handle for a token in ls and revoke. Two tokens with one name would make it ambiguous which one you mean to revoke.

Resolution

  • Pick a different name:

    magus config mcp connector create --name ci-2
    
  • Or revoke the existing one first if you meant to replace it (there is no renew; replacing is revoke-then-mint). The new token gets a new id, so records made under the old one still name the old one:

    magus config mcp connector revoke ci
    magus config mcp connector create --name ci
    

See also

MGS9005authconnectorconsoletokencreatename
Last updated (f0d4ffc9)
Earlier changes on this page (2)

Full history ↗ · Blame source ↗

Glossary

CI

An ordinary magusfile-defined target you compose yourself with magus\needs - magus does not hardcode its stages. Magus.RunCI treats it specially only in that it strips the rw charm, it is the anchor magus affected ci keys off, and a selected scope with no project declaring it is a load error rather than a silent no-op. See targets.

Conventions

This page uses none of the site's convention markers. The full set is on the conventions page.