Update the actions project-level DAST sentence
Why are we doing this work
- The DAST site/scanner profiles are input boxes when they could be dropdowns
- The DAST sentence is a little confusing; reword it
Relevant links
See epic for designs
Implementation plan
MR 1
-
frontend update the policy_action_builder.vue templates to be dropdowns for the project-level -
scannerProfiletemplate (use graphql query similar to dast_scanner_profiles.query.graphql to populate the dropdown) -
siteProfiletemplate (use graphql query similar to dast_site_profiles.query.graphql to populate the dropdown)
-
MR2
-
frontend update the policy_action_builder.vue sentence for DAST (moved to #390166 (closed))
GraphQL queries/mutations
query ReadProfiles($fullPath: ID!) {
project(fullPath: $fullPath) {
dastSiteProfiles {
nodes {
profileName
}
}
dastScannerProfiles {
nodes {
profileName
}
}
}
}
mutation CreateProfiles($fullPath: ID!, $profileName: String!) {
dastScannerProfileCreate(
input: {fullPath: $fullPath, profileName: $profileName, scanType: PASSIVE}
) {
dastScannerProfile {
profileName
}
}
dastSiteProfileCreate(
input: {fullPath: $fullPath, profileName: $profileName, targetUrl: "https://example.com", targetType: WEBSITE}
) {
dastSiteProfile {
profileName
}
}
}
Verification steps
- Upload a GitLab Ultimate license
- Navigate to a group/project => Security & Compliance => Policies => New policy => Scan Execution Policy (e.g. gdk group/gdk project
- Verify changes
- Navigate to a group/project => Security & Compliance => Policies => New policy => Scan Result Policy (e.g. gdk group/gdk project
- Verify no changes have occured
Edited by Alexander Turinske