RFC: migrate scaffolder plugins to Backstage repo #30
Comments
|
A few days ago, one of the key contributors to Backstage brought an interesting RFC from the Backstage repository to my attention. You can find it here: backstage/backstage#20266 Currently, there is an ongoing discussion regarding the best solution, but in the interim, it would be highly beneficial to find a way to update both the azure-devops-scaffolder plugins. If the proposed move outlined in this RFC is contingent on approval within the Backstage RFC, I'd like to suggest two possible approaches: Grant commit and PR approval permissions to someone who can assist in updating the plugins. I'm more than willing to take on this responsibility if you're comfortable with it. If, for any reason, you're unable or unwilling to provide these permissions, would it be feasible to consider forking the repository and publishing it as an @backstage package? I appreciate your consideration and look forward to hearing from you! 😁 |
|
Hey there! I've noticed more and more folks are running into issues with this problem. I really want to find a solution that can help everyone out. I'm up for creating a fork and trying to fix it. If I manage to fix it, I'll publish it under the "@backstage" name. Down the road, when you've got some time, we can chat about merging these fixes and discuss what steps you'd like to take next. I hope you understand how important it is to take action. Thanks a bunch! |
|
Hi! I created 2 temporary npm packages with the fixes! I just did a quick fix until we hear from the owners, be aware that could be done better 😅 But looks like its working good! You can find the README.md with the updated changes you must do . At the end I just published under my personal because 2 reasons:
I tested only on Azure DevOps Server, but as far as I understood the code, it should be working equal for dev.azure.com I will address any issues related to the fixes I've made, but until we receive updates on this situation, I won't be able to handle any other matters at this time. Thank you for your understanding. I understand that there might be distrust about this changes so I courage you to take a look to my forked repos so you can see the all the changes before use the packages: Repositories plugin forked repo In addition I share some links from the official Backstage Discord conversation with one of the main contributors for the azdops stack and the RFC related from the official Backstage repo: I hope this can help to keep updating Backstage until we find a proper solution. Cheers! |
|
@antoniobergas I'm sorry for the very late answer and for leaving the community in the air with their issues. I'll take your suggestion for an internal discussion and will get back to you tomorrow about moving the plugins to the official backstage repo and having it maintained by the community. Cheers |
|
@cr0wnf0x @antoniobergas Hi is there any update on the progress? |
|
Hi @ZOBHeile I have no update yet, maybe the maintainers can shed some light on the matter 🙏 |
|
Hi guys! Is there any news on this? Will appreciate a response to keep this plugins updated for the community, thank you! |
|
Looks like the Backstage team has decided to move forward with a community plugins repo. See backstage/backstage#20266 (comment). Unfortunately they haven't set this up yet. Would appreciate an update on the status here though. We're keen to use these plugins, but are hesitant due to the lack of support. |
|
@cr0wnf0x do we have any update on this as createAzurePipelineAction now fails with latest version upgrade of "@backstage/integration": "^1.6.2" |
|
Note that the Backstage team has started a discussion around a community owned plugins repo. See backstage/community#120 for more details. |
|
@antoniobergas thanks for your fixes that you have made, was going mad trying to fix it myself. Would suggest the maintainers to really look at this, current scaffolder does not work without Antonios fixes. |
|
Hey @antoniobergas @cr0wnf0x. I'm blocked by this and I am considering moving the plugins to the community repo, what should we do about the copyright notice? Should it be the original authors - or are you happy for it to be the same pattern in backstage community repo? |
|
Hi @Phiph , I can't provide information about the copyright since I'm not one of the maintainers of this repository. However, I support moving it as I initially suggested in the original issue. If I may ask, why are you blocked by this? Have you tested my temporary packages? |
|
Ahhh good point I always get mixed up between the 2 packages, I'll try yours out again :) Thanks! Does that mean we're kinda blocked on copyright if we moved the code to backstage community? |
|
Not sure about what can be done with this copyrigh but anyways I think the actual code its just http calls with fetch and maybe a rework using the azure devops node api would be great 😁 |
|
I've tried integrating your packages into backstage, however it looks like the new backend is providing the Type 'ScmIntegrations' and is not assignable to type 'ScmIntegrationRegistry'. I'll try and pick the action to make into backstage community soon. |
|
The packages are not compatible with the new backend system, you need to load them as legacyPlugin |
|
Hi, just wanted to share this Issue I logged in the Backstage Community Plugins repo: backstage/community-plugins#1393. Would very much like to get feedback from the maintainers of this repo before moving forward. |
|
Hi, just following up as I have not heard back? |
As more and more people is using Backstage and by that all Azure DevOps users are using this scaffolder plugins I want to suggest to migrate them to the Backstage repo.
AFAIK Backstage maintainers already recommend officially this plugins in the documentation, so would make sense to move them so the community can take ownership to keep them update?
What you think?
@MatthiasKainer
@hevans-dglcom
@clemensheithecker
The text was updated successfully, but these errors were encountered: