Draft: 17.1 Planning—Secret Detection
🔒 Secure, Secret Detection - Milestone Planning
This is a planning issue for Category:Secret Detection and Category:Code Quality, which is maintained by groupsecret detection.
See the group handbook page for more about this issue and how it fits into group workflows.
In this issue:
Milestone Key Dates
- Duration:
- Release Date:
Narrative
Pre-receive Secret Detection Beta
In %17.0, we made a significant amount of progress and have completed development of the core features that were in scope for Beta! We've also spun up a baseline monitoring dashboard and playbook to help us track the performance of this feature while we enable it across internal GitLab projects, which we've kicked off via Dogfood Pre-receive SD on internal GitLab projects (&13523).
There were a handful of bugs and enhancements identified from those efforts, which we'll look to prioritize in %17.1. In addition to that, we'll look to deliver the following key targets/goal posts:
- Event tracking is completed
- Dogfooding on internal GitLab projects has wrapped up
- Alerting established for key components
- Beta production readiness has been completed
- Beta launch material prepped
By the end of %17.1, we'd like to have Beta polished up and ready for any interested customers to start using!
High-impact updates to the current Secret Detection system
Other expected work
(See direction for discussion of these two themes and how they interact.)
Priorities
Key items to deliver
This section lists items that should be ready to deliver (or at least to move forward). Many of these items should be defined as ~Deliverable items, assuming they are feasible to deliver in the milestone.
Status of this list: Initially reviewed. We will add typemaintenance and typebug items, and ensure that all typefeature work is included, before reviewing the overall list with team members.
Initiative | Issues | DRI |
---|---|---|
Looking forward
This section lists items that are in earlier stages of planning. Refining them is an important part of this milestone because it sets us up to work on them in the following milestones. Primary areas of responsibility are listed, but everyone can contribute!
This is almost certainly more than we can take on. It's generally in priority order (most important at the top).
Initiative | Item | DRI |
---|---|---|
Add detail of potential secrets in client-side ... (#412229) • Dheeraj Joshi • 17.1 |
Please suggest others or add them directly.
Product and UX
This section includes other Product and UX context that may not fit into the Looking forward section above.
Product Manager: @smeadzinger
- Transition tasks
UX Designer: @mfangman
- Design: Pre-receive Secret Dection configuratio... (#451559 - closed) • Michael Fangman • 17.0
- Discover the Jobs to Be Done (JTBD) for Secret ... (ux-research#2707) • Michael Fangman, Erika Feldman • 16.7
Documentation
This section includes group inputs and the plan for Technical Writing in the milestone.
Technical Writing stable counterpart: @rdickenson
- Update documentation, focusing on how instance-... (#451359) • Serena Fang • 17.1
- Add supported token/API key/secret types to doc... (#454905) • Unassigned