VerifiedNote will be 'ok' if SSubContact verified successfully.
Otherwise, there will be there value for VerifiedNote:
1. no such mobile: mobile is not exist, change and try again.
2. incomplete config: tell admin to improve the configuration.
3. service exceptions: try again or connect to admin.
* feat(notify): Add 'get-types' action for ConfigManager
The List interface is only open to administrators,
because we don't want anyone other than administrators
to see the details of the notify configuration.
To let general user to kown available notification channels,
add 'get-types' actions of ConfigManager.
* feat(notify): Check the availability of contact type before creating notification
Creating notification with unconfigured contact type will fail at
sending message. Now, prevent creation in advance.
* feat(notify): Add workwx for NotifyNormal/Important/Critical
* feat(notify): Add Notify about robot in notifyclient
* fix(notify): Init ParentContactType for SSubContact
1. ParentContactType of SSubContact with webconsole type is empty.
2. ParentContactType of others SSubContact is mobile.
* fix(notify): Unverify SSubContact when ParentContactType match
* fix(notify): When no data is initialized, exit directly
* feat(notify): Support update for notify config
* fix(notify): Be compatible with the email configuration
Email config key text changed:
mail.username => username
mail.password => password
mail.smtp.hostname => hostname
mail.smtp.hostport => hostport
* fix(notify): Give users permission to operate receiver
* fix(notify): Allow negative update for receiver
Now, input.Email and input.Mobile can be empty which means
that do not update the corresponding field.
* feat(notify): Support for triggering validation on feishu, dingtalk and worwx
Triggering validation on these contact types means repulling a Contact about them.
* feat(notify): Adds validity period for verify
Verification beyond the expiration date will fail.
* fix(notify): SQuery of scopedomain in FilterByOwner
* refactor(notify): ALL
* feat(climc): Notify v2
* feat: support notify for codegen.py
* delete deprecated code and Maintain SDK compatibility
* Adjust the template for mail validation to support captcha
* fix: The issue of notify refactoring
* add copyright for notifyv2 cli
* Adjust according to the advice of make check
* Remove utils package in notify
* fix import format
* remove redundant Template module
* fix validateCreate and validateUpdate of notifytemplate
* fix update issues of receivers
* fix: Add SetStageComplete in tasks
1. Add same return value with contact GET interface when updating
2. Add pull params for query to pull subcontact by mobile number.
For example, pull user_id from dingtalk throught user's mobile
number.
3. Add corresponding feature based on above for climc.
4. UserCache will try FetchByName if there is no id matched user when
fetching users from KeyStone.
1. Uname is availbale now in api via adding "uname=true" in query.
So we can use uname in climc which is much more visual and use uid in
web client which avoid time-consuming remote calls that may occur.
2. Previously, the template for the message was managed by the
individual sending components. Now, these templats was managed uniformly
by Notify Service so that we can easily add and remove.
3. Now, failure to send a validation message will trigger a notification
to the user via websocket.
rainzm