fix: fixed the move of alerting file#281
Merged
kotharironak merged 1 commit intomainfrom Aug 26, 2021
Merged
Conversation
|
Lets try getting rid of the postgres folder itself and thus the need to duplicate the alerting yml file We can try adding an override for postgres at the top level which overrides the entity-store data base |
findingrish
approved these changes
Aug 26, 2021
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As part of the discussion #276 (comment), it was to keep both mongo and Postgres in sync for using the single command for starting services with alerting component. However, in the previous PR, the alerting file was accidentally removed. Adding it back to a top-level folder.