---
# System prepended metadata

title: Untitled

---

### Feature request

As of now, `catlin` is growing as it's own CLI tool which can be used to manage/interact with tektoncd/catalog. In order to make it available for users there is a need to ship it as a tool which can be used.

## Exfiltrate `catlin` into its own repository

The idea is to move catlin to a separate repository, ie, moving it out of plumbing repository so that it can be managed easily and we can start releasing it as a separate binary.
<!-- The reason behind moving catlin to a separate repo is it will be managed
 easily and also we can start releasing the binaries of it so that it is easy for
 users to use it -->

**Advantages**
* Having it in a separate repo would be easily managed
* We could have a CI setup for the repository 

With additions of more command in catlin like

- `catlin validate` - To validate if the resource follows the Catalog Organization rules
- `catlin lint` - To lint the resources
- `catlin bump` - To bump the version of resource

We can also think of some commands to add in catlin like
- `catlin create` - To create a new resource 
- `catlin diff` - To get the difference between successive versions of task

So it would be nice to have catlin as it's own repo 

## Alternative - Club Catlin with `tkn`

* The other options will be to ship/club catlin within `tkn`

**Advantages**
* This would help the user to not download a separate binary if they have
 `tkn` already installed
* No overhead for Tekton admins - need not to maintain an extra repository

**Disadvantages**
* Managing catlin in `tkn` might be cumbersome

<!-- Please describe the feature request and why you would like to have it -->

### Use case

<!-- Please add a concrete use case to demonstrate how such a feature would add value for the user. If you don't have a use case for your feature, please remove this section (however providing a good use case increases the likelihood to be picked up) -->
