Skip to content
This repository was archived by the owner on Feb 2, 2026. It is now read-only.
This repository was archived by the owner on Feb 2, 2026. It is now read-only.

normalize functionality of onyo new --clone and onyo new --template #777

@TobiasKadelka

Description

@TobiasKadelka

In my opinion, the major difference between onyo new --clone and onyo new --template should be how they tab-complete. Functionaly they are doing the same: let the user specify a yaml file that is used as a base for the new asset.

In practice, there are different limitations where we disallow certain locations for the yaml files, like in #775.

I propose that onyo new --clone and onyo new --template should both allow to use a yaml file from anywhere as a base for the new asset, and only are different in regards to tab-completion. And indeed, onyo new --clone does allow this basically for any file (it only misses to check if the file actually exists, see #774).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions