CBAPI-5253: Update Alert YAML with new fields #497
Merged
Conversation
This file contains 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
avanbrunt-cb
reviewed
Apr 8, 2024
avanbrunt-cb
approved these changes
Apr 9, 2024
…_file link from Alert
abowersox-cb
force-pushed
the
CBAPI-5253_alert_yaml
branch
from
35661ee
to
02a8658
Compare
emitreva-cb
approved these changes
Apr 18, 2024
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.
Pull request checklist
Please check if your PR fulfills the following requirements:
What is the ticket or issue number?
https://jira.carbonblack.local/browse/CBAPI-5253
Pull Request Description
Modified documentation for Alerts to include a link to the Developer Network describing all fields.
Does this introduce a breaking change?
How Has This Been Tested?
Unit tests run to verify slight changes to code (for generating class docstrings) had no ill effect.