CLI Reference section

[pileks]

Remaining work:

• expand run command / get feedback from owner ( @Niraj-Kamdar )
• expand infra command / get feedback from owner
• expand deploy command / get feedback from owner
• expand on codegen's -s, --script option Seems relatively unused and not documented elsewhere - can do as a separate PR if need be.
• generally expand on the -c, --client-config option Wherever it’s needed, has links to the explanation

[cbrzn]

I have mixed feelings because this is super cool, but in other commands when it comes to manifest we redirect users to documentation - Should that happen here too?

[pileks]

I agree that this would be much better suited to live within the docs repo.

Now that I look at it, https://docs.polywrap.io/quick-start/workflows/running-workflows seems outdated. Maybe rename it to Runnning tests and update with information found here.

What do you think?
CC @dOrgJelli @krisbitney

[krisbitney]

That's a good idea. I think it should also be added to the manifest package readme so we can prepare for the future when our reference documentation is created by copying the readmes into the docs

[cbrzn]

Should we add an example of how a custom client config file looks like? Usually, I would go to test-cases but would be cool if the dev, when reading this for the first time, have an idea of how to do things? Just thinking out loud feel free to ignore this hehe

[pileks]

That was my thought initially too, but then I linked to a few places with the custom client config.

Now that you commented the same thing, I think I could add it where it belongs.

Maybe a separate "Custom client config" mini-section, with the various options linking to it.