DGNum/uptime-kuma-api
6
0
Fork 0
Code Issues 17 Pull requests 5 Projects Releases 24 Packages Wiki Activity Actions

Fixed datatype for smtpSecure property to bool #69

Open
BergCyrill wants to merge 1 commit from BergCyrill/bugfix/no-ref/fix-smtpSecure-datatype into master
pull from: BergCyrill/bugfix/no-ref/fix-smtpSecure-datatype
merge into: DGNum:master
Conversation 0 Commits 1 Files changed 1 +1 -1
BergCyrill commented 2024-04-05 11:49:16 +02:00 (Migrated from github.com)
Copy link

We were having issues when using the uptime-kuma-api to configure a notification with type "smtp".
After some troubleshooting and viewing entries in the kuma.db we had pinned down the issue due to a wrong datatype of the smtpSecure property in the notification provider.

This PR fixes this issue - we have tested this modification in our environment successfully.

We were having issues when using the uptime-kuma-api to configure a notification with type "smtp". After some troubleshooting and viewing entries in the kuma.db we had pinned down the issue due to a wrong datatype of the smtpSecure property in the notification provider. This PR fixes this issue - we have tested this modification in our environment successfully.
👍 1
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin BergCyrill/bugfix/no-ref/fix-smtpSecure-datatype:BergCyrill/bugfix/no-ref/fix-smtpSecure-datatype
git checkout BergCyrill/bugfix/no-ref/fix-smtpSecure-datatype

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git checkout master
git merge --no-ff BergCyrill/bugfix/no-ref/fix-smtpSecure-datatype
git checkout BergCyrill/bugfix/no-ref/fix-smtpSecure-datatype
git rebase master
git checkout master
git merge --ff-only BergCyrill/bugfix/no-ref/fix-smtpSecure-datatype
git checkout BergCyrill/bugfix/no-ref/fix-smtpSecure-datatype
git rebase master
git checkout master
git merge --no-ff BergCyrill/bugfix/no-ref/fix-smtpSecure-datatype
git checkout master
git merge --squash BergCyrill/bugfix/no-ref/fix-smtpSecure-datatype
git checkout master
git merge --ff-only BergCyrill/bugfix/no-ref/fix-smtpSecure-datatype
git checkout master
git merge BergCyrill/bugfix/no-ref/fix-smtpSecure-datatype
git push origin master
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug

Something isn't working

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
invalid

This doesn't seem right

  
question

Further information is requested

  
wontfix

This will not be worked on

  
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: DGNum/uptime-kuma-api#69
No description provided.
Delete branch "BergCyrill/bugfix/no-ref/fix-smtpSecure-datatype"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?