feat: move most of the plugins to new backend system #1304
Conversation
|
Do we need a version upgrade to 1.24 as well to support the backend system ? or not much changes and makes sense to do it together? It looks like a lot of code changes right now and not sure what related to what exactly :D |
|
Yes we do as for example the scaffolder mock action context is not available earlier. Also some exports missing from backstage/backend-plugin-api before 1.24. |
|
And yes, it's quite a big change and doesn't include even all of the plugins. So some work still required. |
| @@ -0,0 +1,41 @@ | |||
| --- | |||
There was a problem hiding this comment.
Most of our plugins are past 1.x so there should be some minor bumps in here
|
This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution! |
|
bumped the plugin's versions to the backstage version 1.25.0 so this PR shouldn't to handle that anymore |
|
@drodil this is great work. I am just realizing that I may have stood on your toes with the backend integration for the rag-ai-backend yesterday. Sorry about that, I had intended to get a feel for the process and didn't realise you had actually started the work. What can we do to help you get this merged? |
|
Probably should abandon this and do the migration one plugin at a time. Otherwise it's just too much 😅 |
|
@drodil sounds like a good plan! |
|
@drodil I had an idea that we could create an issue listing all of the plugins that need migrating as tasks and then take owners for the migration of each plugin one by one. What do you think? |
|
@punkle sounds like a good idea! |
|
This PR could be used as an example/reference for the migration. But I will close this now. |
|
👉 #1325 |
Closes #1294
✔️ Checklist
yarn changesetin the root)