notification-controller
notification-controller copied to clipboard
Create a new flag to block use of HTTP endpoints for provider
A new flag could be created to block the use of HTTP endpoints for acquiring sources.
When enabled, the flag would not allow the use of the http
scheme across all controller-level objects.
:memo: To do:
- [ ] Disable HTTP scheme for
GenericProvider
. - [ ] Disable HTTP scheme for
SlackProvider
. - [ ] Disable HTTP scheme for
GrafanaProvider
. - [ ] Disable HTTP scheme for
DiscordProvider
. - [ ] Disable HTTP scheme for
MSTeamsProvider
. - [ ] Disable HTTP scheme for
RocketProvider
. - [ ] Disable HTTP scheme for
GitHubDispatchProvider
. - [ ] Disable HTTP scheme for
GitHubProvider
. - [ ] Disable HTTP scheme for
GitLabProvider
. - [ ] Disable HTTP scheme for
BitbucketProvider
. - [ ] Disable HTTP scheme for
AzureDevOpsProvider
. - [ ] Disable HTTP scheme for
GoogleChatProvider
. - [ ] Disable HTTP scheme for
WebexProvider
. - [ ] Disable HTTP scheme for
SentryProvider
. - [ ] Disable HTTP scheme for
AzureEventHubProvider
. - [ ] Disable HTTP scheme for
TelegramProvider
. - [ ] Disable HTTP scheme for
LarkProvider
. - [ ] Disable HTTP scheme for
Matrix
. - [ ] Disable HTTP scheme for
OpsgenieProvider
. - [ ] Disable HTTP scheme for
AlertManagerProvider
.
@pjbgf I would like to work on this