Skip to content
This repository has been archived by the owner on Feb 15, 2024. It is now read-only.

Expose Teams notifications rate limit setting #88

Merged
merged 1 commit into from
Jul 11, 2020

Conversation

atc0005
Copy link
Owner

@atc0005 atc0005 commented Jul 11, 2020

SUMMARY

As a follow-up to GH-87, this commit exposes a new setting that
allows directly configuring the rate limit used for Teams
notifications. GH-3 will be responsible for exposing the same
setting for email notifications.

CHANGES

REFERENCES

SUMMARY

As a follow-up to GH-87, this commit exposes a new setting that
allows directly configuring the rate limit used for Teams
notifications. GH-3 will be responsible for exposing the same
setting for email notifications.

CHANGES

- update documentation to note new setting
  - README
  - GoDoc
  - configure

- configuration file
  - new `rate_limit` setting

- code
  - remove rate limit constants in favor of external settings (email
    rate limit setting scheduled for GH-3) and default const value if
    not specified externally
  - new `TeamsNotificationRateLimit` getter func
  - new `EmailNotificationRateLimit` getter func
    - stub only; further work scheduled for GH-3

REFERENCES

refs GH-87, GH-85, GH-19, GH-3
@atc0005 atc0005 added documentation Improvements or additions to documentation enhancement New feature or request notification email msteams config labels Jul 11, 2020
@atc0005 atc0005 added this to the v0.3.0 milestone Jul 11, 2020
@atc0005 atc0005 self-assigned this Jul 11, 2020
@atc0005 atc0005 merged commit 1fee0ac into master Jul 11, 2020
@atc0005 atc0005 deleted the i85-notification-delay-config-changes-followup-pr branch July 11, 2020 11:14
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
config documentation Improvements or additions to documentation email enhancement New feature or request msteams notification
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Notification delays and timeouts are not clear
1 participant