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.

Sign up for GitHub

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

Jump to bottom

Backend Port of Alerts Schema Changes Including Anomaly Alerts #466

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

Backend Port of Alerts Schema Changes Including Anomaly Alerts #466

wants to merge 6 commits into from

Conversation

colehpage
Copy link
Contributor

No description provided.

@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Jul 9, 2024 •
edited
Loading

⚠️ No Changeset found

Latest commit: b3469a0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@colehpage colehpage changed the title rough cp - backend alerts changes Anomaly Alerts - Backend Port Jul 9, 2024
@colehpage colehpage changed the title Anomaly Alerts - Backend Port Backend Port of Alerts Schema Changes Including Anomaly Alerts Jul 10, 2024
colehpage
colehpage commented Jul 10, 2024
View reviewed changes
packages/api/src/tasks/index.ts
Comment on lines +24 to +27
// TODO: rename to check-users-alerts
case 'check-alerts':
await checkAlerts();
await checkUserAlerts();
break;
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in EE we have this rename TODO - for this OSS port can we update it in this version because there aren't AWS tasks reliant on the existing naming convention and updating the docker-compose files would be enough, or would that break existing setups in a way we want to avoid 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@colehpage