3 ms·
> Tell us your hopes and dreams for a Cloudflare-wide CLI It'd be great if the Wrangler CLI could display the required API token permissions upfront during loc
by 8cvor6j844qw_d6 6mo ago
> Tell us your hopes and dreams for a Cloudflare-wide CLI
It'd be great if the Wrangler CLI could display the required API token permissions upfront during local dev, so you know exactly what to provision before deploying. Even better if there were something like a `cf permissions check` command that tells you what's missing or unneeded perms with an API key.
- contrahax 6mo agoA doctor command that does this is always nice! Wish more services would have this
- jbethune 6mo agoI would second this. Would be very helpful. Had a fat finger issue a while ago that this would have saved.
- LaurensBER 6mo agoThat would be glorious! If ChatGPT doesn't get the permissions right on the first try I know that I'm going to have to spend the next hours reading the documentation or trying random combinations to get a token that works.
- fragmede 6mo agoWhy is "on the first try" so important? What's wrong with telling it your end goal and letting it figure out the exact right combo while you go off and work on something else?
- martyz 6mo agoBecause I don’t want the earth to melt. Maybe if we’re all a bit more efficient we can postpone our doom for a bit.
- duc_minh 6mo agoThat's also my experience. If it does not work on the first try, the model will likely continue to struggle with the problem, unless I babysit it. So I prefer to dig through the source of truth, which also helps me build my mental model around the problem.
- csomar 6mo agoMaybe even better: create that key for you.
- tstrimple 6mo agoI think this boils down to more discoverability of the entire API. While I'm not a fan of GraphQL necessarily, it does provide the tools for very robust LLM usage typically because of the discoverability and HATEOAS aspects they actually follow compared to most "REST" APIs. I would love if LLMs could learn everything they need to about an API just by following links from its root entry point. That drastically cuts down on the "ingested knowledge" and documentation reads (of the wrong version) it needs to perform. Outdated documentation can often be worse than no documentation if the tool has the capability of helping you "discover" its features and capabilities.