feat(crons): Add owner field to MonitorConfig#5610
Open
julwhitney13 wants to merge 1 commit intogetsentry:masterfrom
Open
feat(crons): Add owner field to MonitorConfig#5610julwhitney13 wants to merge 1 commit intogetsentry:masterfrom
julwhitney13 wants to merge 1 commit intogetsentry:masterfrom
Conversation
Support assigning monitor ownership to teams or users via the `owner` field in monitor_config. Format: "team:6" or "user:51". Refs getsentry#5609
Contributor
Semver Impact of This PR🟡 Minor (new features) 📋 Changelog PreviewThis is how your changes will appear in the changelog. New Features ✨
Bug Fixes 🐛
Documentation 📚
Internal Changes 🔧
🤖 This preview updates automatically when you update the PR. |
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds support for the
ownerfield inMonitorConfigto enable monitor ownership assignment to teams or users. This allows developers to organize and route cron monitors within their organization without needing to use the Sentry REST API separately.Description
ownerfield (optional, format:"team:6"or"user:51") toMonitorConfigTypedDictownerfield is properly serialized in check-in payloadIssues
Reminders
tox -e linters.feat:,fix:,ref:,meta:)