-
Notifications
You must be signed in to change notification settings - Fork 544
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
#2044 reenable proxy_url #2050
#2044 reenable proxy_url #2050
Conversation
5588172
to
a63f010
Compare
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 for opening this PR. I prefer to keep it disallowed by default, but I'm open to add an "advanced" configuration option to enable it. The configuration option should be mentioned in the doc at docs/sources/operators-guide/securing/securing-alertmanager.md
.
a63f010
to
fa5c527
Compare
updated based on #2044 (comment) |
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, thanks for the contribution!
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 for working on this! Can you rebase main
, please?
@@ -32,7 +32,7 @@ | |||
* [BUGFIX] Ring: fix bug where instances may appear unhealthy in the hash ring web UI even though they are not. #1933 | |||
* [BUGFIX] API: gzip is now enforced when identity encoding is explicitly rejected. #1864 | |||
* [BUGFIX] Fix panic at startup when Mimir is running in monolithic mode and query sharding is enabled. #2036 | |||
|
|||
* [CHANGE] Re-enable the `proxy_url` option for receiver configuration. #2044 |
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.
A couple of comments about this:
- Please link the PR number
#2050
instead of the issue one - We're used to group CHANGELOG entries together, so CHANGE first, then FEATURE, then ENHANCEMENT and finally BUGFIX. See our contributing guidelines for more info: https://github.com/grafana/mimir/tree/main/docs/internal/contributing#changelog
- CHANGE is for breaking changes, but this is not a breaking change. ENHANCEMENT looks a better fit.
@@ -422,15 +422,9 @@ func validateReceiverHTTPConfig(cfg commoncfg.HTTPClientConfig) error { | |||
if cfg.BearerTokenFile != "" { | |||
return errPasswordFileNotAllowed | |||
} | |||
if cfg.ProxyURL.URL != nil { | |||
return errProxyURLNotAllowed |
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.
Are we still using errProxyURLNotAllowed
? I would have expected that variable to be removed too.
if cfg.OAuth2 != nil && cfg.OAuth2.ClientSecretFile != "" { | ||
return errOAuth2SecretFileNotAllowed | ||
} | ||
if cfg.OAuth2 != nil && cfg.OAuth2.ProxyURL.URL != nil { |
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.
Earlier today I opened the PR #2076 to test the firewall works with cfg.ProxyURL.URL
. Do think it's feasible to have a similar test on cfg.OAuth2.ProxyURL.URL
too?
This PR was mostly good. I'm taking over to get it through the finish line. |
Superseeded by #2317. |
What this PR does
It re-enables the proxy_url option for alertmanager receivers.
See #2044 and the related cortex PR: cortexproject/cortex#4741
Which issue(s) this PR fixes or relates to
Fixes #2044
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]