From 46a27a652539399947b1348c3174f18d7a9b510b Mon Sep 17 00:00:00 2001 From: Amy Qualls <aqualls@gitlab.com> Date: Thu, 23 Jun 2022 19:04:17 +0000 Subject: [PATCH] Placeholder to start a merge request This commit makes a tiny change, so I can start a merge request. I don't have the real answer to what stage or group this work needs to be assigned to, but by starting a merge request, I can assign it to the people who DO know. --- doc/development/appsec/index.md | 35 ++++++-------------------- doc/development/feature_development.md | 1 - 2 files changed, 7 insertions(+), 29 deletions(-) diff --git a/doc/development/appsec/index.md b/doc/development/appsec/index.md index 2ece3fdf4bf00..8361170c3d2e4 100644 --- a/doc/development/appsec/index.md +++ b/doc/development/appsec/index.md @@ -1,32 +1,11 @@ --- -stage: Secure, Protect -group: all -info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments -type: index, dev, reference +redirect_to: '../index.md' +remove_date: '2022-09-23' --- -# Application Security development documentation +This document was moved to [another location](../index.md). -Development guides that are specific to the stages that work on Application Security features are listed here. - -Please go to [Application Security](../../user/application_security/index.md) if you are looking for documentation on how to use those features. - -## Namespaces - -Application Security code in the Rails monolith is organized into the following namespaces, which generally follows -the feature categories in the [Secure](https://about.gitlab.com/stages-devops-lifecycle/secure/) and [Protect](https://about.gitlab.com/stages-devops-lifecycle/protect/) stages. - -- `AppSec`: shared code. - - `AppSec::ContainerScanning`: Container Scanning code. - - `AppSec::Dast`: DAST code. - - `AppSec::DependencyScanning`: Dependency Scanning code. - - `AppSec::Fuzzing::API`: API Fuzzing code. - - `AppSec::Fuzzing::Coverage`: Coverage Fuzzing code. - - `AppSec::Fuzzing`: Shared fuzzing code. - - `AppSec::LicenseCompliance`: License Compliance code. - - `AppSec::Sast`: SAST code. - - `AppSec::SecretDetection`: Secret Detection code. - - `AppSec::VulnMgmt`: Vulnerability Management code. - -Most AppSec code does not conform to these namespace guidelines. When developing, make an effort -to move existing code into the appropriate namespace whenever possible. +<!-- This redirect file can be deleted after <2022-09-23>. --> +<!-- Redirects that point to other docs in the same project expire in three months. --> +<!-- Redirects that point to docs in a different project or site (for example, link is not relative and starts with `https:`) expire in one year. --> +<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/redirects.html --> diff --git a/doc/development/feature_development.md b/doc/development/feature_development.md index 539746f3e4e67..36a75a6167414 100644 --- a/doc/development/feature_development.md +++ b/doc/development/feature_development.md @@ -174,7 +174,6 @@ See [database guidelines](database/index.md). ## Domain-specific guides - [CI/CD development documentation](cicd/index.md) -- [AppSec development documentation](appsec/index.md) ## Technical Reference by Group -- GitLab