Circle CI Plugin Backstage

[sudden loom]

Our company is currently using Backstage and we have currently gone through the backend migration. We have replicated almost all the features that we have setup currrently, but the one plugin that seems to be broken (401 unauthorised missing tokens) is the Circle CI plugin.

Before hand we were using the @backstage/plugins-circleci package but have migrated to the new one. We had no success and reverted back but still no fix.

Having looked at the repo for the plugin, it looks like development has halted and the support has kind of dropped off - has anyone had any success with the plugin since migrating to the new backend?

Cheers

[tacit dove]

Hi @sudden loom, that plugins uses the proxy based on looking at their code - https://github.com/CircleCI-Public/backstage-plugin/blob/main/plugins/circleci/src/api/CircleCIApi.ts - the only option I can think of to make this work isn't great, you would have to set credentials: dangerously-allow-unauthenticated as per the docs here: https://backstage.io/docs/plugins/proxying/#configuration

Often the fix on the plugin side is just to use the FetchApi which would include the needed token but in this case the way they have their code I'm not sure that's going to be an easy thing to do 😦