Hey everyone, I am Josef dejar and I work in the compliance group of the government stage. As a back-end engineer today, I'm gonna demonstrate the new feature that we have created in gitlab 15 6, which is setting a default compliance framework for the group. So, let's start I'll be using this issue. Reproduce group for demonstrating this particular feature: uh let's go to settings general settings and take a look at the already created compliance framework, so the group has any so we can see that this group has one compliance framework uh with the name of gdpr.

That's already created uh I'll just go to the graphql dashboard and see and query the list of compliance Frameworks in this group. We can see that we have one compliance framework with the name of gdpr and the default value is set as false. So this is not the default framework of the group. So what this means is, if I go back and try to create a new project inside this group, let's name it as project a and create this project.

Since the gdpr compliance framework was not the default framework, it should not get automatically attached to the newly created project, which is the case. If you reload, we don't see any compliance framework associated with this project. Now, let's go back to the documentation and see how we can create a framework and make it set it as the default framework, so I'll I'll just use this example. Mutation, I'll copy this and I'll go back to the graphql Explorer I'll paste. This and I'll fix the name space path, which would be issue reproduce in my case.

So what we're doing is we're creating a compliance framework with the name of socks and we're setting the default value as true for this particular framework. So I'll just run this and see what happens so. You can see that a new compliance framework has been created and the default value is set to true. If we go now. If you try to query the list of compliance Frameworks for this namespace again, we should get two Frameworks. Now the first one was gdpr. The new is socks.

The this has the default value set to true. So what this means is, if I go back and try to create a new project, the newly created compliance framework should automatically get attached to the new project. So let's take a look at that.

So we can see that the this particular project is has already associated with the newly created compliance framework and on the other hand, if you go back to the first project, it's still the same and it doesn't have the compliance framework Associated to it. So this means that the projects that have uh that that were created prior to setting the default compliance framework are not affected. At All by this and the other thing is, we cannot delete the default compliance framework if you try to delete the default.

One it'll fail with an error, so this is very useful for groups where they want to set a default compliance framework and want that framework to be associated with all the projects inside that group. Thanks for watching.