Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Abandoned Plugin] OctoPrint-Webhooks #1156

Closed
derekantrican opened this issue Feb 1, 2023 · 9 comments · Fixed by #1157
Closed

[Abandoned Plugin] OctoPrint-Webhooks #1156

derekantrican opened this issue Feb 1, 2023 · 9 comments · Fixed by #1157

Comments

@derekantrican
Copy link
Contributor

Which Plugin?

https://plugins.octoprint.org/plugins/webhooks

Link to ticket on plugin's issue tracker confirming abandonment

2blane/OctoPrint-Webhooks#38

Is there someone open to adopting it?

@derekantrican

@jneilliii
Copy link
Contributor

jneilliii commented Feb 1, 2023

@derekantrican since you already have a fork it's just a matter of updating the plugin listing page to point to yours and add you to the authors list. Make sure to change the software update hook to point to your repo and bump the version and release with the new version number. If you need any pointers, I'd look at this adoption PR as reference of what they changed as part of the process, and don't hesitate to ask any questions for clarification.

#1027

@derekantrican
Copy link
Contributor Author

Thanks! I'll make sure I move my pending changes to a different branch so the "master" mirrors the current state of the official repo.

Once I've updated the update hook (and anything else) do I just come back here and give you the "go ahead" to update the plugin listing page?

@jneilliii
Copy link
Contributor

Submit a PR similar to the one above referencing this issue.

@derekantrican
Copy link
Contributor Author

derekantrican commented Feb 1, 2023

@jneilliii Thanks! At what point can I expect this to show up on plugins.octoprint.org and (nvm - looks like that's already been updated) the alert to users in their octoprint interface?

@jneilliii
Copy link
Contributor

It typically is within 24 hours, but that depends on the user's configured TTL for plugin update notices.

@derekantrican
Copy link
Contributor Author

@jneilliii I got the notifications on my octoprint instance today (both the "new maintainer" notice and the notification of update available). Out of curiosity I clicked the "Update" button in the notification for the new version and it failed (probably expectedly as the old plugin is still pointing at the old repo and the new version doesn't exist at that repo - hence the notice to uninstall & reinstall).

Is there a chance Octoprint could have a "migrate & update" sort of feature for this case where the plugin has moved repos? Or perhaps a "uninstall & reinstall" option if the plugin fails to update?

@cp2004
Copy link
Member

cp2004 commented Feb 2, 2023

The pip field must also be specified in the overlays file here:

webhooks:
user: derekantrican

Similar to this, it overrides the pip field in the SW update config, so it should look the same as what you have the SW update hook looking like at the moment.

ledstripcontrol:
user: gbonesso
pip: https://github.com/gbonesso/OctoPrint-LEDStripControl/archive/{target_version}.zip

@derekantrican
Copy link
Contributor Author

Thank you! I'll make that change

@jneilliii
Copy link
Contributor

Ah, thanks for the clarification @cp2004. I thought updating the user alone was enough to handle the redirect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants