Closed BHSPitMonkey closed 1 year ago
Some additional comments:
[project.optional-dependencies]
was the correct call here, but I figured it was safe to follow the example set by the Twilio notifier. Please let me know if there's a better way to go (or change at will)!hatch
; Apologies if I've missed a step relating to the addition of the new package.Nice, this looks very solid. Apprise seems like it'll fit a ton of different notification use cases. I will get a closer look at it later to make sure all the hatch stuff is set up right and the tests are passing. Thank you for the contribution 🏕️
Hey @BHSPitMonkey, hope you don't mind, I squashed your commits into one, and then added a couple commits to resolve the issues. I'm new to hatch as well so it took me a sec.
Changes Made
Python 3.9
This adds some dependencies that more recent of Python don't need:tada: This PR is included in version 0.20.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
Apologies for what? Easiest time I've had landing a change in a long time :wink: Thanks for the help!
Description
This PR adds Apprise as a supported notification provider.
Apprise is a popular Python library that exposes the ability to notify using dozens of popular notification and messaging services (and protocols), including Discord, Home Assistant, and MQTT.
Users configure Apprise by specifying a URL which contains details of the service being used and any relevant authentication tokens. Some examples borrowed from their documentation:
discord://webhook_id/webhook_token
hassio://hostname/accesstoken
mqtt://user@hostname/topic
Has This Been Tested?
I've tested this locally using:
after configuring a
APPRISE_URL
in my.camply
file (using the interactive configurator).Apprise URLs take many forms depending on the notification service being used. Refer to the documentation for supported schemes and examples.
Checklist:
.pre_commit
on all my code