Welcome to rhiza-cli Discussions!

[HarryCampion]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[HarryCampion]

@tschm Looking to move some of the scripts over to the cli, like we discussed. Wonder if the best way to do it is to move them over to rhiza-cli or a new repo like rhiza-tools and then can install the tools as an extra like rhiza-cli[tools]? Could be overkill...

[HarryCampion]

I figured we can have rhiza-tools but provide a light wrapper around the cli to invoke those tools? eg base installation of rhiza-cli you get the lightweight interface but you could do uv tool install rhiza-cli[tools] to get some of the extras? I am not sure that is the right approach, but figured it could be a neat way to expose extras under the same interface but not face bloating in rhiza-cli. I can have a bit more thought.

[HarryCampion]

Marimushka and mini book remain standalone, but things like bump and release can be in rhiza-cli

[HarryCampion]

reducing complexity of the scripts a bit and allowing better testing from rhiza-cli instead.

[HarryCampion]

But I think some of these cool command line hacks could be extra installables? Then exposed in a very lightweight way through the Makefile.

[tschm]

Let's have a call at some time if you have time. Take for example bump. It's a big sh script that is copied over. An alternative would be to hide it in some package and pip install it every time. However, this would make people nervous. Having this explicit script is not bad after all.

[HarryCampion]

It is a just a skeleton at the moment but my hope is to wrap up some of those scripts into useful set of tools that can be installed as a plugin for rhiza https://github.com/Jebel-Quant/rhiza-tools.

You could then run

uvx "rhiza[tools]" bump

This would mean we can strip out the logic from the bump.sh script and release.sh and just invoke uvx "rhiza[tools]" instead. We'd keep the .sh as these are important for allowing customisations through the make interface but it starts to build out some robust tooling, but they would just call uvx "rhiza[tools]" tools bump instead.

You can of course install standalone using uvx rhiza-tools --help.

Next steps I need to test the plugin feature is working well so I will want to publish the skeleton as it is into pypi, we get the rhiza-tools name then. When you have time can you set up a OIDC permission flow with pypi so the release flow works?

[HarryCampion]

An example setting it up locally