Skip to content

CLI vpc-peering get doesn't resolve short IDs #469

@poyrazK

Description

@poyrazK

Why is this an issue?

The cloud vpc-peering get command doesn't resolve short IDs to full UUIDs, returning "invalid vpc peering id" instead.

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 vpc-peering get command handler.

Category

  • Small
  • Medium
  • Large

Severity

  • Low
  • Medium
  • High
  • Critical

Steps to reproduce

cloud vpc-peering list  # Shows short ID: c7064c3c
cloud vpc-peering get c7064c3c
# Error: api error: {"error":{"type":"INVALID_INPUT","message":"invalid vpc peering id","code":"INVALID_INPUT"}}

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