Spike: Where are License Scanning reports used in the codebase?

Time-boxed: 1 day

Topic to Evaluate

Before updating the Rails app to leverage license data stored in the primary DB, we need to know where legacy License Scanning reports are used. This is prep work for implementation issues of Use License Scanning service (&8532 - closed).

Tasks to Evaluate

  • Identify bits of code that directly use License Scanning reports: models, controllers, services, workers, etc.
  • Optionally, make specific suggestions on how to update the code, and add abstraction layers to switch between the old implementation and the old old
  • Update &8532 (closed) and/or its issues.

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.

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

Last updated by this job

Discoto Settings 
---
summary:
  max_items: -1
  sort_by: created
  sort_direction: ascending

See the settings schema for details.

Edited by Fabien Catteau