CLI fn-schedule logs doesn't resolve short IDs

[poyrazK]

Why is this an issue?

The cloud fn-schedule logs command accepts [id] but doesn't resolve short IDs, failing with "invalid schedule id" instead of looking up the full UUID.

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 fn-schedule logs command handler.

Category

• Small
• Medium
• Large

Severity

• Low
• Medium
• High
• Critical

Steps to reproduce

cloud fn-schedule logs 1eb33bb9
# Output: Error: api error: {"error":{"type":"INVALID_INPUT","message":"invalid schedule id","code":"INVALID_INPUT"}}

# Note: cloud fn-schedule list works with short IDs (1eb33bb9 resolves)