Summary
stackctl stack create --definition klaravik-dev fails with "Stack definition not found" because --definition only accepts UUIDs. Users must look up the UUID first via stackctl definition list, then copy-paste it.
Expected behavior
--definition should accept either a name or a UUID, matching how <name|id> works for stack commands. If the name is ambiguous (multiple definitions with the same name), return an error listing the matches.
Example
# Should work
stackctl stack create --name my-stack --definition klaravik-dev --branch master
# Currently required
stackctl stack create --name my-stack --definition e9af3b10-4633-436b-a131-975a3b598e3e --branch master
Where to fix
In cmd/stack.go, the create command should resolve the --definition value through the definitions API (similar to how resolveStackID resolves stack names).
Summary
stackctl stack create --definition klaravik-devfails with "Stack definition not found" because--definitiononly accepts UUIDs. Users must look up the UUID first viastackctl definition list, then copy-paste it.Expected behavior
--definitionshould accept either a name or a UUID, matching how<name|id>works for stack commands. If the name is ambiguous (multiple definitions with the same name), return an error listing the matches.Example
Where to fix
In
cmd/stack.go, the create command should resolve the--definitionvalue through the definitions API (similar to howresolveStackIDresolves stack names).