Add a readme

[errordeveloper]

It's long overdue! I know that more detailed usage examples would be quite good, but I'd leave that for the next PR.

I'm really keen to hear feedback about the description, whether it's clear enough or a bit too "out there"... Please do keep in mind that this tool is relatively low-level, it's currently for the kind of users who'd otherwise run flux push artifact or possibly go DIY.

[lnovara]

Following a call with @errordeveloper, I try to summarise my thoughts about Tape.

I really like the simplicity of the tool and how it helps in framing the configuration as data.

I would better highlight Tape's relation with tools such as Kustomize and Helm and also that, right now, adoption of Tape is limited to Flux users since AFAIK is the only GitOps tool that understands OCI artifacts.

Nice work! 🙌

[errordeveloper]

@lnovara thank you! I've added a paragraph about the ecosystem, please let me know if it's any good :)

[stefanprodan]

I would replace artefact with artifact, as this is the spelling used by OCI, Flux, etc.

[errordeveloper]

@stefanprodan @slimslenderslacks both of you mentioned that showing OCI JSON manifests would be helpful, I've added an example that shows all that there is. PTAL, whenever you have a chance =)

It's quite verbose, maybe I can use <details/> for some of these JSON objects, but the readme is a bit wordy overall anyway, I wish it to be shorter. Perhaps I can worry about that later.

[stefanprodan]

At the top there is git switch 6.4.1 but in here in shows master. I suggest to redo examples for the Git tag.

[errordeveloper]

git switch 6.4.1 actually fails, have to use git switch --detach 6.4.1... 🙃

[errordeveloper]

Well spotted! I've fixed the output and opened #13 to address tags in attestations.

[stefanprodan]

LGTM 💯

[ipedrazas]

lgtm

[kipz]

Minor language suggestions. Feel free to ignore. Looks good to me :)