Making Automatically Compliant Design Documents With Infrastructure as Code
summary
Claims a reproducible pipeline that turns plain text design data into automation code so parameter sheets stop being a manual error source. Uses a CSV-based semantic design format stored in Git, a simple editor that exports to Excel for deliverables, and Python converters that emit Terraform / Ansible artifacts and tests. Demonstrates reusable snippets where VMware VM creation separates logic and data, reduces ad‑hoc SSH checks, and notes the system is internal (not OSS) while covering a migration from a decade of manual work.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:41Agenda of this talk
- 4:16Role of System Integrators in the IT Services Industry System Integrators (Siers) are total coordinators that undertake development operations, ete in information system development
- 6:21Design Documents in Deliverables
- 7:04Appearance of Parameter Sheet: Example
- 8:54Expectations for Parameter Sheets and Issues • Expectations for parameter sheets
- 10:153 Key Factors of Parameter Sheets: The 1st Factor
- 13:19Reality of the Parameter Sheets
- 15:13The History of Our lac Approaches legend Manual task
- 16:55Our Initial Approach: Extraction Data From Unified F
- 18:30The Overview of Our New lac Approach Point 1: Separation of view and data
- 19:54Integration With Version Control and Reuse as Best Practices
- 21:20Separation of logic and data
- 22:29Best Case Scenario: Example of Parameter Change
- 24:43Conclusion
related talks
59mEverything as a Code
50mContinuous and Automated Documentation Docs As Code in Practice
46mBest Practices for Keeping Architecture Documentation Up to Date
35mThe practical implementation of Documentation as Code
44mPushing documentation (so it doesn't hurt anymore)
47mEngineering Documentation
47mDocumentation Is Fine, Don't Worry
25mBuilding Docs like Code: Continuous Integration for Documentation