axodotdev / gazenot Goto Github PK

In particular make #8 configurable by an env-var.

cargo-dist should re-expose these by generating ci that reads SECRETS with the same name and lowers them to env.

Need for cargo dist host --steps=check. It checks if you auth is properly setup for the packages you care about, without actually doing side-effectful operations.

We currently spawn as many things concurrently as we can, and as seen in #8 this can cause 3-stooges syndrome where tasks start timing out even though each one individually could easily resolve in time. We should have some upper limit on concurrency to manage this, or... do something more robust.

Code is there, needs data format

Could be more like our other client crates with things much more granular, for now not caring about it.

• Ensure these have the right builtin value
• Make them overrideable with env-vars
• Make them overrideable with a builder..?