-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
5
-
False
-
False
-
KONFLUX-1501 - Threat model for SP release-engineering workspace
-
-
-
Sprint 258, Pipelines Sprint Crookshanks 5, Pipelines Sprint Crookshanks 7, Pipelines Sprint Crookshanks 8
Story (Required)
As a pipeline service developer trying to improve security on RHATP I want to enable TLS for connections between Results API and DB.
Background (Required)
The functionality was added to Tekton Results upstream and rolling the change downstream is tracked here PLNSRVCE-1437.
https://github.com/tektoncd/results/blob/main/docs/database-ssl-mode-custom-CA-cert.md documents the process.
Out of scope
<Defines what is not included in this story>
Approach (Required)
<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>
Dependencies
<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>
Acceptance Criteria (Mandatory)
<Describe edge cases to consider when implementing the story and defining tests>
<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>
Done Checklist
- Code is completed, reviewed, documented and checked in
- Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
- Continuous Delivery pipeline(s) is able to proceed with new code included
- Customer facing documentation, API docs etc. are produced/updated, reviewed and published
- Acceptance criteria are met