Skip to content

feat: Add ScanningAlertsClientV1 with support for Scanning Alerts #200

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 10 commits into from
Sep 28, 2021

Conversation

tembleking
Copy link
Member

The old method add_alert doesn't work correctly, because it lacks of a type field, that's required, and update_alert is not very usable, because the user must understand how to modify it correctly.

The new add_repository_alert, add_runtime_alert, update_repository_alert and update_runtime_alert methods are a bit easier to use and are correctly tested.

@tembleking tembleking self-assigned this Sep 28, 2021
@nestorsalceda nestorsalceda merged commit 96d84e6 into master Sep 28, 2021
@nestorsalceda nestorsalceda deleted the feat-scanning-alerts branch September 28, 2021 11:29
tembleking added a commit that referenced this pull request Jul 11, 2022
* feat(scanning): Add support for runtime alert creation

* feat(scanning): Add support for repository alert creation

* ci(scanning): Add test that retrieves an alert

* feat(scanning): Add support for runtime alert update

* feat(scanning): Add support for repository alert update

* refactor(scanning): Extract ScanningAlertsClientV1 client

* docs: Add usage examples

* docs: Add SdScanningClient documentation autogeneration

* fix(lint): Expand imports

* lint: Fix linting errors and add EditorConfig
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants