Fix n plus one issue ci build dast profile

added backend label

	9 Warnings
	b3070bbc: The commit body should not contain more than 72 characters per line. For more information, take a look at our Commit message guidelines.
	05f1ce88: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	d9bf9256: The commit body should not contain more than 72 characters per line. For more information, take a look at our Commit message guidelines.
	df2efd71: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.
	c3cfdc11: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.
	342c6572: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.
	081cad73: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.
	df967e3a: The commit body should not contain more than 72 characters per line. For more information, take a look at our Commit message guidelines.
	5e31dbc2: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.

	1 Message
	This merge request adds or changes files that require a review from the Database team.

This merge request requires a database review. To make sure these changes are reviewed, take the following steps:

Ensure the merge request has database and databasereview pending labels. If the merge request modifies database files, Danger will do this for you.
Prepare your MR for database review according to the docs.
Assign and mention the database reviewer suggested by Reviewer Roulette.

If you no longer require a database review, you can remove this suggestion by removing the database label and re-running the danger-review job.

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	Marc Shaw (`@marc_shaw`) (UTC+1)	Tetiana Chupryna (`@brytannia`) (UTC+2)
database	Maxime Orefice (`@morefice`) (UTC+1)	Patrick Bair (`@pbair`) (UTC-5)

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. 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

Setting label groupdynamic analysis based on @mc_rocha's group.

added groupdynamic analysis label

Setting label(s) devopssecure sectionsec based on groupdynamic analysis.

added devopssecure sectionsec labels

added 1 commit

29ecee5f - Update DAST Association Service

Fix n plus one issue ci build dast profile

What does this MR do and why?

Before

After

Screenshots or screen recordings

How to set up and validate locally

MR acceptance checklist

Merge request reports

Activity

Reviewer roulette