Split Secure features into more granular features
Description
NOTE: the below description is specific to SAST but this change should be made for all devopssecure features.
We are treating the existing devopssecure categories as features within the codebase. We should instead break the categories into their composite features.
The sast
feature is not granular enough as it's currently specified at the EE level, but is partially available to all levels.
Proposal
Replace Secure features with more specific features. In the case of Category:SAST, https://docs.gitlab.com/ee/user/application_security/sast/index.html#summary-of-features-per-tier lays out what should be available.
Tasks
-
Create a feature string for all top-level features that aren't available to all levels. -
Replace usage of the sast
string feature value with policy references when possible -
Deprecation notice regarding split of sast feature (this may not be needed)
🤖
Auto-Summary Discoto Usage
Points
Discussion points are declared by headings, list items, and single lines that start with the text (case-insensitive)
point:
. For example, the following are all valid points:
#### POINT: This is a point
* point: This is a point
+ Point: This is a point
- pOINT: This is a point
point: This is a **point**
Note that any markdown used in the point text will also be propagated into the topic summaries.
Outcomes
Outcomes define the decisions or resolutions of a discussion. Once outcomes are defined, sub-topics and points are collapsed underneath the outcomes.
Outcomes are declared in a similar manner as points:
#### OUTCOME: This is an outcome
* outcome: This is an outcome
+ Outcome: This is an outcome
- oUTCOME: This is an outcome
outcome: This is an outcome
Note that multiple outcomes may be declared for each topic.
Topics
Topics can be stand-alone and contained within an issuable (epic, issue, MR), or can be inline.
Inline topics are defined by creating a new thread (discussion) where the first line of the first comment is a heading that starts with (case-insensitive)
topic:
. For example, the following are all valid topics:
# Topic: Inline discussion topic 1
## TOPIC: **{+A Green, bolded topic+}**
### tOpIc: Another topic
Quick Actions
Action Description /discuss sub-topic TITLE
Create an issue for a sub-topic. Does not work in epics /discuss link ISSUABLE-LINK
Link an issuable as a child of this discussion Discussion-Size Indicators
The relative size of the discussion occurring within a topic and its sub-topics is indicated via braille dots.
More dots means that more points or sub-topics exist within a given topic.
Examples:
- TOPIC
⣿⣿⡆
A large discussion occurred here- TOPIC
⣇
A smaller discussion occurred here
Last updated by this job
TOPIC
⡇
OUTCOME: do not store vulnerability data for non-ultimate tiers #248105 (comment 655373719)TOPIC
⣧
Discoto Settings
---
summary:
max_items: -1
sort_by: created
sort_direction: ascending
See the settings schema for details.