Support APPRISE_URI environment variable

[visch]

💡 The Idea
https://github.com/caronc/apprise?tab=readme-ov-file#command-line-usage

It'd be great if one of these were

export APPRISE_URI="ses://[email protected]/client_id/clietn_secret/to_email1/to_emailN"
apprise -vv -t 'my title' -b 'my notification body'

This is similar-ish to #1156 , but I think it's a much easier implementation.

I do this all the time with custom notifications with https://hub.meltano.com/loaders/target-apprise but right now I have a use case with GitHub actions that would be very nice. Someone made a GitHub action here: https://github.com/marketplace/actions/apprise-notification, which also does this, but I think implementing this feature would make this work in many CI automation use cases.

🔨 Breaking Feature
I don't think so

[visch]

  - name: Failure notifications
    if: ${{ failure() }}
    run: apprise -t "Title" -b "Body" ${{ secrets.APPRISE_URI }} -v

To be fair this was really easy too with a uv tool install apprise

[caronc]

Using the secrets is a much safer choice IMO, good on you for figuring out a very good workaround

[visch]

@caronc I disagree but 🤷 to each their own, thanks for this tool I love it

[caronc]

So do you feel the environment variable should still kick in if defined? Not sure why you closed the ticket a few hours after opening it then 🙃. I'll reopen and keep it queued.

This request is different than the issue you referenced. The one you linked to requests dynamic variables in the configuration file. You're proposing using pre loaded URLs if none were otherwise specified and no configuration file was found. Would that statement be correct?

[caronc]

See attached PR; the good news is there actualy already is and APPRISE_URLS for you to use as an environment variable; it was not documented (but in the source code) :).

I updated the documentation and added more variables for the future.

[caronc]

Code mered; closing ticket

[visch]

So do you feel the environment variable should still kick in if defined? Not sure why you closed the ticket a few hours after opening it then 🙃. I'll reopen and keep it queued.

I found a solution so I"m good to go, hate leaving something open if I don't need it.

This request is different than the issue you referenced. The one you linked to requests dynamic variables in the configuration file. You're proposing using pre loaded URLs if none were otherwise specified and no configuration file was found. Would that statement be correct?

Yeah that's why I said "similar-ish" and still opened a new ticket.

Code mered; closing ticket

Thank you so much! Will be really nice to use, I'm a bit nervous about the comma/space delimiter but most api keys are friendly enough about commas that we should be ok.