Add `carti publish` option `--repo` to specify repository

[miltonjonat]

At the moment carti publish always adds the specified bundle to a local bundles.json repository index file, which must later be manually made available by the user.

Adding an option --repo <uri> would allow the user to specify an alternative repository index file.

Ideally, we would also like to be able to allow that <uri> to be a remote location, so that the bundle can be effectively published in one go. If possible, we could support different submission procedures depending on the specified protocol, such as sending a POST request to an HTTP/HTTPS URL.

• Example: carti publish s3 --bucket xyz scrypt-hash --repo https://xyz.io/repo-endpoint

[zcstarr]

Still not sure on this point. I think this makes the workflow a little less clear. I think right now the flow is something like
one simple rule, you want something to be discoverable push it to git somewhere.

I think the listing file has to be its own separate command. Otherwise it's impossible to infer intent. Aka. I made a modification to the listing file that I don't intend to commit, but I wanted to publish new data about this bundle to the listing, but not the other things.

Something like the following might be a better fit then it's clear what you're publishing to where.

carti publish s3 --type bundle --bucket xyz scrypt-hash
carti publish git --type listing --repo somelocation

This way you're explicitly saying you want to push up everything that's in a bundles.json to some location.

[miltonjonat]

My thinking was: when you publish a bundle, you are always including it in some repo index. If you do not specify anything, it's the local bundles.json repo index. Otherwise, you can specify an alternative local path, or a remote URL. I'm not sure what the confusion is.

On the other hand, your suggestion for carti publish git sounds confusing for me, because carti publish s3 publishes a bundle whereas carti publish git would be publishing the repo index. In my view those are two very different concepts for the same carti publish command.

[zcstarr]

for clarity the git in
carti publish git is just to say that you're talking to git, in my mind you could also publish the bundle asset to git so it's really just a storage layer.

That aside, what's the user use case for cross publishing bundles.json ? What scenario do they need to incrementally add to git vs work directly within their development workflow? Maybe for me the largest open question is what does this look like from a CI perspective?

[miltonjonat]

Ok, let's rewind here:

1. Sorry, I hadn't seen the --type bundle and --type listing. So forget what I said about the confusion there, my bad.
2. I am not quite sure how Carti would use git as a storage layer: Carti would commit the file to git?
3. What do you mean by cross-publishing bundles.json? I never intended to publish the same bundles.json to multiple places. My idea was just to have a way for the user to inform which repo index/listing the published bundle should be included in. So for a CI it would mean that whenever Carti publishes a given bundle it could update a listing x on a remote server somewhere.
4. I'm trying to exercise what would be the CI workflow without --repo. Say we have project /my-user/my-util-drive that builds a flash drive with cross-compiled code. Its CI would download bundles.json from a separate repo (e.g., /my-user/my-carti-repo), publish the asset (say, pointing to a github URI), and then commit that bundles.json back to /my-user/my-carti-repo?