Expose `vulnerability_events` field in REST integrations API endpoints
What does this MR do and why?
The vulnerability events have been around since 14.3 49e788b9 but was previously missing from integration API responses. This change exposes the field in the integrations API.
How to set up and validate locally
Visit the integrations API endpoints:
http://gdk.test:3000/api/v4/projects/<project_id>/integrations?private_token=<private_token>
-
http://gdk.test:3000/api/v4/projects/<project_id>/integrations/jenkins?private_token=<private_token>
(or any individual integration endpoint)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Merge request reports
Activity
assigned to @.luke
added typefeature label
added devopsmanage sectiondev labels
changed milestone to %16.4
1 Message This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
-
doc/api/integrations.md
(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
Reviewer roulette
Changes that require review have been detected!
Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:
Category Reviewer Maintainer backend Rad Batnag (
@radbatnag
) (UTC+8, 4 hours behind@.luke
)Charlie Ablett (
@cablett
) (UTC+12, same timezone as@.luke
)Please check reviewer's status!
Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger-
marked the checklist item I have evaluated the MR acceptance checklist for this MR. as completed
added 1 commit
- 7dccd780 - Expose `vulnerability_events` integrations field
- A deleted user
added documentation label
added 1 commit
- 35798baf - Expose `vulnerability_events` integrations field
- Resolved by Luke Duncalfe
requested review from @eread
@.luke Some end-to-end (E2E) tests should run based on the stage label.
Please start the
trigger-omnibus-and-follow-up-e2e
job in theqa
stage and ensure tests in thefollow-up-e2e:package-and-test-ee
pipeline pass before this MR is merged. (E2E tests are computationally intensive and don't run automatically for every push/rebase, so we ask you to run this job manually at least once.)To run all E2E tests, apply the pipeline:run-all-e2e label and run a new pipeline.
E2E test jobs are allowed to fail due to flakiness. See current failures at the latest pipeline triage issue.
Once done, apply the
emoji on this comment.Team members only: for any questions or help, reach out on the internal
#quality
Slack channel.added Technical Writing docsfeature labels
removed review request for @eread
Allure report
allure-report-publisher
generated test report!e2e-test-on-gdk:
test report for 223ba34cexpand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Data Stores | 20 | 0 | 0 | 1 | 20 | ❗ | | Manage | 13 | 0 | 1 | 0 | 14 | ✅ | | Plan | 51 | 0 | 0 | 0 | 51 | ✅ | | Create | 38 | 0 | 0 | 0 | 38 | ✅ | | Verify | 8 | 0 | 0 | 0 | 8 | ✅ | | Govern | 34 | 0 | 0 | 0 | 34 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 164 | 0 | 1 | 1 | 165 | ❗ | +-------------+--------+--------+---------+-------+-------+--------+
e2e-package-and-test:
test report for 774209f4expand test summary
+-----------------------------------------------------------------------+ | suites summary | +------------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +------------------+--------+--------+---------+-------+-------+--------+ | Manage | 158 | 0 | 13 | 3 | 171 | ❗ | | Create | 151 | 0 | 35 | 1 | 186 | ❗ | | Configure | 1 | 0 | 0 | 0 | 1 | ✅ | | Package | 0 | 0 | 2 | 0 | 2 | ➖ | | Plan | 8 | 0 | 0 | 0 | 8 | ✅ | | Monitor | 8 | 0 | 0 | 0 | 8 | ✅ | | Data Stores | 4 | 0 | 0 | 0 | 4 | ✅ | | Govern | 4 | 0 | 0 | 0 | 4 | ✅ | | Framework sanity | 0 | 0 | 2 | 0 | 2 | ➖ | +------------------+--------+--------+---------+-------+-------+--------+ | Total | 334 | 0 | 52 | 4 | 386 | ❗ | +------------------+--------+--------+---------+-------+-------+--------+
requested review from @eread
- Resolved by Bob Van Landuyt
Hi, @bmarjanovic
! Could you please give this MR its first backend review? Thank you!
requested review from @bmarjanovic
@eread
, thanks for approving this merge request.This is the first time the merge request has been approved. To ensure full test coverage, a new pipeline will be started shortly.
For more info, please refer to the following links:
added pipeline:mr-approved label
- Resolved by Luke Duncalfe
requested review from @reprazent and removed review request for @bmarjanovic
removed review request for @eread
- Resolved by Bob Van Landuyt
@.luke Terribly sorry for not getting to this Friday
. One more suggestion because of that.
removed review request for @reprazent
changed milestone to %16.5
requested review from @reprazent
enabled an automatic merge when the pipeline for a69c26ab succeeds
Thanks @.luke
mentioned in commit 9ced950c
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-staging label and removed workflowproduction label
added releasedcandidate label
changed milestone to %16.4
mentioned in merge request !132306 (merged)
added releasedpublished label and removed releasedcandidate label
mentioned in merge request kubitus-project/kubitus-installer!2437 (merged)