notification
notification copied to clipboard
Notification is an enterprise-grade general-purpose high-performance notification system.
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.0.0-20190520210107-018c4d40a106 to 0.7.0. Commits See full diff in compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter...
Bumps [github.com/gin-gonic/gin](https://github.com/gin-gonic/gin) from 1.3.0 to 1.7.7. Release notes Sourced from github.com/gin-gonic/gin's releases. Release v1.7.7 BUGFIXES Fixed X-Forwarded-For unsafe handling of CVE-2020-28483 #2844, closed issue #2862 Tree: updated the code logic...
告警如何对接钉钉
请问有这个计划么?有计划的话现在做到什么程度了
POST /v1/notifications 接口,设置address_info为已删除或不存在的addresslist: { "content_type": "other", "title": "test_title", "content":"{\"html\":\"test_content_html\", \"normal\":\"test_content_normal\"}", "owner": "KubeSphere", "address_info": "[\"adl-111\"]" } 未进行校验控制,可以成功调用
调用PUT /v1/addresslists/{addresslist}修改addresslist时,当address_id中包含有重复的address时: { "addresslist": "11", "address_id": [ "addr-zV2QNkjkYqMP","addr-zV2QNkjkYqMP" ] } 可以成功操作,但查询此address,此address会存在两条相同的记录: { "total_count": 2, "address_set": [ { "address_id": "addr-zV2QNkjkYqMP", "address_list_id": "adl-57ZORpm996Yv", "address": "[email protected]", "remarks": "", "verification_code": "", "status": "active", "create_time":...
创建address时,若设置的email和系统中存在的处于active状态的address的email重复时,不能成功创建; 但在调用PUT /v1/addresses/{address}接口,修改某address A时,设置的email和系统中已存在的处于active状态的address B的email重复时,可以成功修改,未进行校验控制;
以下几种情况: 1、删除address接口,设置address_id参数为不存在的或已删除的address_id时 2、创建或修改addresslist接口中,设置参数address_id为已删除的或不存在的address时,或者address_id字段值为空 3、删除addresslist接口,当设置的参数addresslist id为不存在或已删除的或disabled的addresslist时 调用接口时,上述情况提示信息均为列表[[XXXXX]]中某些元素不合法,此提示信息不够准确,且‘不合法’一般是针对字符格式校验不通过时的提示信息,建议上述情况下,优化提示信息,针对不同的情况给出准确的提示信息。
调用GET /v1/addresses/,设置search_word为已存在的address_id,address,notify_type,或remarks字段时,查询结果为空
调用/v1/notifications接口创建通知时,接口文档中未指明content为必填项; 且当未设置content字段时,提示信息为:unexpected end of JSON input,建议优化提示信息。 另:address_info也为必填字段,文档中未说明
GET /v1/addresses,设置了address_id和search_word查询字段进行查询, 查询结果不正确,查询结果中包含了address_id不是所设置的address_id的address