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.

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

make tls option InsecureSkipVerify configurable by alertmanager #1140

Closed
wants to merge 1 commit into from

Conversation

victoryang
Copy link

When we try to send mails to notify clients, and if it requires TLS, the TLS option InsecureSkipVerify should be configurable with alertmanager's configuration. This PR is to add InsecureSkipVerify into alertmanager's global configuration.

@stuartnelson3
Copy link
Contributor

PLEASE don't close and open a new pull request because CI fails. You can restart CI. This creates a ton of noise and is very annoying.

@victoryang
Copy link
Author

Sorry for that...

@brancz
Copy link
Member

brancz commented Dec 14, 2017

I was very much hoping we could get the entire HTTP config a la this, to make sure everything we know being a valid use case can be enabled.

But we never go to agreement on how to continue. /cc @fabxc @brian-brazil

@simonpasquier
Copy link
Member

Closed by #1528

hh pushed a commit to ii/alertmanager that referenced this pull request Nov 26, 2018
* Change Dfly's CPU counting frequency, see: prometheus/node_exporter#1129

* Convert Dfly's CPU unit into second

Signed-off-by: iori-yja <fivo.11235813@gmail.com>
hh pushed a commit to ii/alertmanager that referenced this pull request Nov 30, 2018
* Change Dfly's CPU counting frequency, see: prometheus/node_exporter#1129

* Convert Dfly's CPU unit into second

Signed-off-by: iori-yja <fivo.11235813@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants