Render form input screen and package description for a local package using Kurtosis Web (without package catalog)

[galenmarchetti]

Background & motivation

I want to render a form input and the nice description for my package in the frontend, but I have to wait for 2 hours / the Github API to play nicely for the package catalog to show it

Desired behaviour

I want to render a form input and the nice description for my package in the frontend just using kurtosis web and not needing to wait for the package catalog

How important is this to you?

Painful; the lack of this feature makes using Kurtosis frictionful.

[mieubrisse]

I'd like to kill multiple birds with one stone with the design for this, by merging the "Catalog" and "Manual" package configuration screens. Ideally, what I'd like to see:

FIRST: there is only one package configuration screen. On it, the package locator is a form field. When a package locator is entered in the form field, the indexer is hit. If there is an indexer entry, the result is displayed as the form we know and love. If there is no entry, then some message saying "No package run metadata detected. Add some by visiting ".

SECOND: There is also a refresh/reindex button. Clicking it will request that the indexer reindex the package right then. If it's successful, then the form fields we know and love are displayed. If not, then the reason for the indexing failure is displayed.

THIRD: the package catalog is just an entrypoint to the package configuration screen. Literally the only thing it does is send you to the package configuration screen and prefill the package locator field.

Birds killed:

• Currently, when you have a manually-entered package (for whatever reason), you only get the nasty JSON input
• Users don't have to wait for 2h to get a refresh for changes to existing packages
• New users can get their packages indexed right away
• Users can see how changes to the docstring change the form, and get an error if it's not valid