Remove monitoring config, use messaging instead
Closed this issue · 6 comments
Describe the bug
In the past, we introduced a "monitoring" config that can perform a POST request to an endpoint to automatically monitor new package releases. As this functionality is no longer used, it can be removed. It was used as a trigger to wheel build pipeline. We can fully utilize messaging for this purpose.
Expected behavior
Remove monitoring config and monitoring related code in sources.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Still relevant and should be easy to fix.
/remove-lifecycle stale
/priority important-longterm
/kind feature
/kind demo
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@sesheta: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/remove-lifecycle rotten