GitLab Govern:Threat Insights Features & Demos, 1 Sep 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Vulnerability History Discussions Powered by GraphQL

Description

This video is an MR Walkthrough which describes how the feature works. Here's the link to the MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/69353

A

Hi everyone- this is sawash from group thread insights and in this video I'm going to walk you through the changes regarding the vulnerability history, migration to graphql.

A

So previously we were using uh the rest endpoints for this, and this video is going to walk you through the last piece, which is fetching the notes through graphql and so yeah. Let's get started, so I am right now in a in a vulnerability details page um the state is deducted, so there is uh right now here in the footer part, there is um graphql query which polls for the discussions and a discussion is generated through a status change.

A

So, for instance, if I confirm this and change the status here, you see that a new discussion appears. So I can go ahead and then type a comment.

A

This is a comment and save it, and then you will see that it appears here. I can edit it.

A

Still works and I can delete it now next time I change the status. Another thread will appear so here I can go ahead and then type something this for variability is now resolved and I can save the comment um so the way it works. There is a graphql query which pulls for the discussions every five seconds.

A

So if I go ahead and then visit another tab and then change the status here and immediately go back to the first step, you will see that it will appear here after a while.

A

And when this changes it also uh in the code, there is also an event which basically tells this page to refresh the header part. So, as you can see, the status is now confirmed, so I'm changing tabs again, and this is confirmed and if I change it to resolve, you will see that first, it's confirmed and then it automatically uh it is updated to result, and if I scroll down, you will see that there is. There. Is this discussion, um so that's it with this.

A

Mr um now, the whole vulnerability history part is powered by graphql. This was the last comment uh last comment so um yeah. That's it thanks for watching the video and have a great day.