Repository navigation
openapi: add investigation target purpose and optional datasource_id - #1043
Merged
Merged
Conversation
Document the per-entry purpose field (one-sentence plain text, max 512 bytes) and allow QueryInvestigationTarget.datasource_id to be omitted so the query runs on the alert event's own datasource. Align go-sdk notes with the same contract.
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
1 participant
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
purposetoInvestigationTargetin the OpenAPI contracts (en/zh, including monitors module specs): one-sentence plain text, max 512 bytes, not a template.QueryInvestigationTarget.datasource_idoptional (omit or 0 = the alert event's own datasource) so the public contract matches backend behavior.Verification
python3 scripts/lint_openapi.py— OK, 12 spec files, no violations.