db: update the database layer to support alerts #1116
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
oh yeah, after every database change, you want to run: That'll run the |
rdimitrov
force-pushed
the
db-updates
branch
6 times, most recently
from
5a5bc1e
to
0d9dc05
Compare
Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
rdimitrov
changed the title
Signed-off-by: Radoslav Dimitrov <radoslav@stacklok.com>
JAORMX
approved these changes
Oct 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The following PR will include the database changes related to implementing alerts and any refactoring around that.
The goal of this is to update and apply the database changes without breaking any existing functionality and without introducing anything new in terms of features yet.
Fixes: #1114