-
Notifications
You must be signed in to change notification settings - Fork 816
Change config flags, add flags to disable Alertmanager notifications methods: email & webhoook #2187
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
Conversation
Signed-off-by: Wing924 <[email protected]>
Signed-off-by: Wing924 <[email protected]>
Signed-off-by: Wing924 <[email protected]>
So many flags seems like overkill to me. |
you’re right. we don’t need so many flags. |
@@ -108,6 +108,10 @@ Where default_value is the value to use if the environment variable is undefined | |||
# The ruler_config configures the Cortex ruler. | |||
[ruler: <ruler_config>] | |||
|
|||
# The configs_api_config configures the configs API used by the 'configs' | |||
# service to expose APIs to manage them. | |||
[configs_api: <configs_api_config>] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From the configuration perspective, I'm a bit concerned having another root block config. Ideally we should have 1 root config block for each service (even if in the past some weird things have been done), so think it would be better adding the NotificationsConfig
as part of the ConfigDB
config.
Signed-off-by: Wing924 <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with minor nit around the error message.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very good job! I love your contributions: clean and concise ❤️
I left few minor comments, then will LGTM. Thanks!
Signed-off-by: Wing924 <[email protected]>
Signed-off-by: Wing924 <[email protected]>
Signed-off-by: Wing924 <[email protected]>
Signed-off-by: Wing924 <[email protected]>
@pracucci |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Signed-off-by: Wing924 <[email protected]>
Signed-off-by: Wing924 <[email protected]>
Signed-off-by: Wing924 <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Wing924 for addressing my comment! I left few comments and then it will be good to go to me! Thanks 🙏
Signed-off-by: Wing924 <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, with a nit!
Signed-off-by: Wing924 <[email protected]>
Please edit the PR title and description to cover all that it now changes. |
Signed-off-by: Wing924 <[email protected]>
What this PR does:
Added flags to disable Alertmanager notifications methods.
-database.*
->-configs.database.*
-database.migrations
->-configs.database.migrations-dir
configdb.uri:
->configs.database.uri:
configdb.migrationsdir:
->configs.database.migrations_dir:
configdb.passwordfile:
->configs.database.password_file:
Which issue(s) this PR fixes:
The Alertmanager notifications via email is disabled in cortex.
I tested on my cluster and found email works without any problems.
I asked on Slack and found the reason is email may attack SaaS.
I other words, we can enable email on on-premises.
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]