Design#
This document describes the architecture of ansible-collection.
User perspective, audience, features, user requirements, and acceptance scenarios are defined in System Requirements. This design document focuses on architecture, technical decisions, runtime behavior, and implementation structure.
The structure follows arc42 with the user-perspective parts reduced to short references instead of duplicated content.
Structure#
Introduction and Goals#
This design document explains how the system realizes the requirements defined in System Requirements.
Architecture Constraints#
Context and Scope#
See Context and Scope.
Solution Strategy#
See Solution Strategy.
Building Block View#
See Building Block View.
Runtime View#
See Runtime View.
Deployment View#
See Deployment View.
Crosscutting Concepts#
Security Considerations#
Architecture Decisions#
Confd Access-Spike Evaluation#
Quality Requirements#
See Quality Requirements.
Risks and Technical Debt#
Domain Model#
The entity model, aggregate boundaries, and per-use-case EventStorming
diagrams derived from the Gherkin scenarios in specs/ansible_modules and
specs/ansible_playbook. See Entity Model
Relationship and the Use Case
EventStorming Diagrams.
Glossary#
See the Glossary for terms used across this design document and the Gherkin acceptance scenarios.
Open Issues#
See Open Issues.