Closed caronc closed 5 months ago
This branch needs testing; hopefully @portalzine or @xgaia can give it a shot (instructions above) and let me know?
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (
31a4f2e
) 99.27% compared to head (a17cebc
) 99.27%. Report is 1 commits behind head on master.
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Currently running it from the apprise-api. Will do a fresh pure branch install later this week and let you know ...
Tested this with the latest release and I am always getting:
Failed to send Rocket.Chat token:notification: Channel/RoomId is wrong format, or missing from server., error=400.
Tried varies formats:
3 - sends no error message, but never sends the notification itself (no errors in the apprise logs).
Token is fine and channel exists.
The workaround using the api directly works fine json://chat.myhost.com/api/v1/chat.postMessage
, which means that there is something else.
Description:
Related issue (if applicable): #210
Added
token
support to the?mode=
list. The syntax is:{schema}://{user}:{token}@{host}:{port}/{targets}
{schema}://{user}:{token}@{host}/{targets}
Note:
{schema}
is eitherrocket
orrockets
this is similar to
{schema}://{user}:{password}@{host}:{port}/{targets}
. Apprise tries to detect if it was a{password}
or{token}
based on it's length. If the value specified is >32 characters, then it assumes?mode=token
, otherwise it will use?mode=basic
.You can always specific the
mode=<val>
to enforce what you meant.If you specify a
{user}/{token}
, then authentication HTTP requests are skipped and theX-User-Id
andX-Auth-Token
are pre-populated in the headers in advance.Checklist
flake8
)Testing
Anyone can help test this source code as follows: