microcks / microcks-backstage-provider

A provider for Backstage.io allowing to synchronize API entities from Microcks to Backstage
https://microcks.io
Apache License 2.0
9 stars 6 forks source link

Plugin does not work for backstage 1.33 #63

Closed javiermartingonzalez closed 1 day ago

javiermartingonzalez commented 5 days ago

Describe the bug

Hello, Backstage not starting after installing 1.33 version due to plugin-catalog-backend incompatibility. It seems it was not applying the migration and the backend is not starting.

With your last update, you are using @backstage/plugin-catalog-backend@1.27 version and newer version is @backstage/plugin-catalog-backend@1.28

Can you check? Uninstalling Microcks plugin solves the problem

Expected behavior

No response

Actual behavior

2024-11-21T15:35:13.404Z backstage info Plugin initialization in progress, still initializing: 'app' type=initialization C:\Repositorios\idp\backstage\node_modules\@backstage\backend-defaults\node_modules\@backstage\backend-app-api\src\wiring\BackendInitializer.ts:334 throw new ForwardedError( ^

ForwardedError [TypeError]: Plugin 'catalog' startup failed; caused by TypeError: backendOpenapiUtils.createValidatedOpenApiRouterFromGeneratedEndpointMap is not a function at

How to Reproduce?

No response

Microcks version or git rev

No response

Install method (docker-compose, helm chart, operator, docker-desktop extension,...)

No response

Additional information

No response

github-actions[bot] commented 5 days ago

πŸ‘‹ @javiermartingonzalez

Welcome to the Microcks community! πŸ’–

Thanks and congrats πŸŽ‰ for opening your first issue here! Be sure to follow the issue template or please update it accordingly.

πŸ“’ If you're using Microcks in your organization, please add your company name to this list. πŸ™ It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.

If you need to know why and how to add yourself to the list, please read the blog post "Join the Microcks Adopters list and Empower the vibrant open source Community πŸ™Œ"

Hope you have a great time there!

🌟 ~~~~~ 🌟

πŸ“’ If you like Microcks, please ⭐ star ⭐ our repo to support it!

πŸ™ It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.

lbroudoux commented 5 days ago

Oh... I just tested with backstage 1.32 and was hoping to have some time before another API breaking change... Will have a look at it.

lbroudoux commented 2 days ago

Hi @javiermartingonzalez,

I tried reproducing this by directly creating a new backstage 1.33 application and adding the 0.0.6 version of our plugin to it, but I didn't succeed. The plugin is installed correctly and works as expected without errors in the log.

My app packages/backend/package.json actually references @backstage/plugin-catalog-backend": "^1.28.0" as you noticed but this doesn't raise issue with @backstage/plugin-catalog-backend": "^1.27.0 used in the Microcks plugin.

Can you explain the process you followed to get this exception?

javiermartingonzalez commented 1 day ago

Hello again! I think it was something wrong with yarn.lock

Today I deleted the package and Backstage was working. Then, I added it again and it is working. So probably, something wrong with package that was solved after removing and adding again.

Thank you for your support and sorry for the inconveniences