Skip to content

CLI secrets get and secrets rm don't resolve short IDs #474

@poyrazK

Description

@poyrazK

Why is this an issue?

The cloud secrets get and cloud secrets rm commands don't resolve short IDs to full UUIDs. The help text says [id/name] implying both work, but short IDs are rejected with "secret not found".

What is causing it?

The CLI passes the short ID directly to the API without resolving it to a full UUID.

How can it be solved?

Add short ID resolution in the secrets get and secrets rm command handlers.

Category

  • Small
  • Medium
  • Large

Severity

  • Low
  • Medium
  • High
  • Critical

Steps to reproduce

cloud secrets list
# Shows short ID: 78ee1b39

cloud secrets get 78ee1b39
# Error: api error: {"error":{"type":"NOT_FOUND","message":"secret not found","code":"NOT_FOUND"}}

cloud secrets rm 78ee1b39
# Error: api error: {"error":{"type":"NOT_FOUND","message":"secret not found","code":"NOT_FOUND"}}

# But names work:
cloud secrets get my-api-key
# Works correctly

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions