Aramis Sennyey

@drodil Sounds good, I'm still curious if we want this to be attached to the Backstage CLI or if this should start a new CLI that is instance specific? That...

@awanlin I think we can remove https://backstage.io/docs/auth/troubleshooting/ and https://backstage.io/docs/plugins/call-existing-api from the list. AFAICT they're both backend system agnostic - they definitely need a revamp but I think that can be...

👋 , I think you're right on! Would you be open to submitting a PR to fix this as well as add tests?

(assuming CI passes) This should be ready for a rereview. I added clients for todo and search as well. There is unfortunately a weird edge case with search where we...

~Gonna wait for the code piece of the community plugin migration to rebase this one. I'll move the client work for the todo plugin to that repository once this merges.~...

@Rugvip This should be good for a rereview when you get a chance 🙏

@freben Waiting for feedback to my comment [here](https://github.com/backstage/backstage/pull/23661#discussion_r1573486874) - `require.resolve` is having some issues with relative resolution in tests that I think it would run into generally as well.

👋 This should be ready for a re-review!

I think the auth work is 0003? It's getting hard to keep them straight 😅 .

Hey 👋 ! This is a bit of a two-headed problem. 1. Some clients haven't been migrated to the new `fetchApi` in the frontend or pulled code from older implementations....