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

feat: Add notification support #1381

Draft
wants to merge 53 commits into
base: main
Choose a base branch
from
Draft

feat: Add notification support #1381

wants to merge 53 commits into from

Conversation

jorenn92
Copy link
Owner

This PR introduces notification support to Maintainerr. You can now add notification providers via the settings. When creating a rule, you’ll be able to configure which notification provider to use for that rule.

Please note: I’ve only tested this with the Discord and Pushover notification providers. The others have not yet been tested.

@jorenn92 jorenn92 requested a review from benscobie November 18, 2024 15:04
@jorenn92
Copy link
Owner Author

/release-pr

Copy link
Contributor

‼️ There was an error trying to release the PR.

@jorenn92
Copy link
Owner Author

/release-pr

Copy link
Contributor

Released to jorenn92/maintainerr:pr-1381 🚀

@jorenn92
Copy link
Owner Author

The "About to be Handled" notification type is still a work in progress. I’m still getting the cron job fully set up. Once it’s ready, I’ll update this PR.

@jorenn92
Copy link
Owner Author

/release-pr

Copy link
Contributor

Released to jorenn92/maintainerr:pr-1381 🚀

@jorenn92
Copy link
Owner Author

jorenn92 commented Nov 19, 2024

Todo:

  • Remove the 'none' notification type
  • Add the cron timer of the 'Notification timer'-task to the settings (maybe)
  • Configurable messages (Later in a follow up PR)
  • Testing and probably fixing untested notification agents

@benscobie
Copy link
Collaborator

I'll try and get to reviewing this sometime this week.

@jorenn92
Copy link
Owner Author

TODO: There might be a logic issue in how notifications are being sent. In certain parts of the code, I call a method to send a notification to all agents active for a specific notification type. However, it might be possible that the notification is also being sent out for rules that don't have that notification agent configured.

This is not tested though, it's just an afterthought I just had.

@jorenn92
Copy link
Owner Author

/release-pr

jorenn92 and others added 22 commits January 24, 2025 11:33
Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 22.8.7 to 22.9.0.
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

---
updated-dependencies:
- dependency-name: "@types/node"
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps [@nestjs/cli](https://github.com/nestjs/nest-cli) from 10.4.5 to 10.4.7.
- [Release notes](https://github.com/nestjs/nest-cli/releases)
- [Changelog](https://github.com/nestjs/nest-cli/blob/master/.release-it.json)
- [Commits](nestjs/nest-cli@10.4.5...10.4.7)

---
updated-dependencies:
- dependency-name: "@nestjs/cli"
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps [tailwindcss](https://github.com/tailwindlabs/tailwindcss) from 3.4.14 to 3.4.15.
- [Release notes](https://github.com/tailwindlabs/tailwindcss/releases)
- [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/v3.4.15/CHANGELOG.md)
- [Commits](tailwindlabs/tailwindcss@v3.4.14...v3.4.15)

---
updated-dependencies:
- dependency-name: tailwindcss
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps [eslint-config-next](https://github.com/vercel/next.js/tree/HEAD/packages/eslint-config-next) from 15.0.0 to 15.0.3.
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](https://github.com/vercel/next.js/commits/v15.0.3/packages/eslint-config-next)

---
updated-dependencies:
- dependency-name: eslint-config-next
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps [monaco-editor](https://github.com/microsoft/monaco-editor) from 0.51.0 to 0.52.0.
- [Release notes](https://github.com/microsoft/monaco-editor/releases)
- [Changelog](https://github.com/microsoft/monaco-editor/blob/main/CHANGELOG.md)
- [Commits](microsoft/monaco-editor@v0.51.0...v0.52.0)

---
updated-dependencies:
- dependency-name: monaco-editor
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps [@eslint/eslintrc](https://github.com/eslint/eslintrc) from 3.1.0 to 3.2.0.
- [Release notes](https://github.com/eslint/eslintrc/releases)
- [Changelog](https://github.com/eslint/eslintrc/blob/main/CHANGELOG.md)
- [Commits](eslint/eslintrc@v3.1.0...v3.2.0)

---
updated-dependencies:
- dependency-name: "@eslint/eslintrc"
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps [eslint](https://github.com/eslint/eslint) from 9.12.0 to 9.15.0.
- [Release notes](https://github.com/eslint/eslint/releases)
- [Changelog](https://github.com/eslint/eslint/blob/main/CHANGELOG.md)
- [Commits](eslint/eslint@v9.12.0...v9.15.0)

---
updated-dependencies:
- dependency-name: eslint
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Files were owned by node:node with 755. If you override the user then they won't have permission to replace __PATH_PREFIX__ on startup. This change makes the UI folder writable by anybody. At first I didn't like this, but as it was 755 before then the node user could already write files. Really this is no worse as we're in a container.
@jorenn92
Copy link
Owner Author

/release-pr

Copy link
Contributor

Released to jorenn92/maintainerr:pr-1381 🚀

@jorenn92
Copy link
Owner Author

/release-pr

Copy link
Contributor

Released to jorenn92/maintainerr:pr-1381 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants