GitLab Fulfillment Demos, 25 Sep 2023

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: Add ApplicationRateLimit for Group update API

Description

MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/132053

A

Hello, this is the demo for this Mr, where I'm uh I did a new application rate limit called update, namespace name in order to limit the number of call made from gitlab to customers Dot whenever uh the actual the actual the group API is used.

A

This is just an Abuse Prevention type of measure, more details in the related issue, so to test that we have like two windows here: two terminals, a gitlab terminal window and the second window, being the customer's Dot I'm, going to fire up a console for customer dots same here, and here I'm just going to show the code and in the application limiter for the sake of this test, I'm setting the threshold to two here.

A

So what I'm gonna do is I'm gonna trigger the update, namespace name uh um limiter, I'm gonna hit it by triggering by our firing updates on the same group three times, which means that uh two times uh the namespace on the customer's Dot site would be updated, but not the third time around.

A

Let's give this a try, so, on the gitlab side, I am going to work off of um no we're on gitlab here. So it's this one.

A

And um and here.

A

There we go, that's what we want to check and that's uh that's the the order that we are going to be updating asynchronously after making the API Call to um to gitlab. So we will work off of this uh order, slash gitlab, namespace here and updating this name.

A

Let's do this via call command that updates the group 113 um with the name updated name, one.

A

Before doing that, I'm just going to check out the logs for rails background jobs.

A

I just want to make sure that the job, because it's not synchronous job that is fired to uh to update their customers, dot side there we go namespace, sync namespace, name Walker.

A

If I'm checking the name of this group here on gitlab, it's good and here updated name one. So that's one update.

A

For the same group.

A

Let's update the name again.

A

All right there we go.

A

A

And uh oh, no, it's not the right yeah there we go updated name too, and since we set the limit to 2, we should be updating only the gitlab side. Here.

A

There we go updated, name three but I, don't know I, don't think I've seen any jobs being triggered, so that should remain updated. Name too.

A

Yep, a Target.