Details
-
Architectural Decision
-
Resolution: Done
-
None
-
None
Description
Why now? The ability to obtain software configuration has been requested for PSIs
Scope: All software
Quality: Availability (this affects our ability to recover if software is discovered to be faulty), Testability (needed for reproducing problem)
We need to decide how to characterise a deployed software system, so we can reliably reproduce it. This is going to be really important once we get to non-trivial deployments.
At this point we only seem to have a "current" version of the software, which is implicitly assumed to be used for all deployment and debugging efforts. This already causes a great deal of friction due to different parts of the system occassionally going out of sync.
Attachments
Issue Links
- is assumed by
-
SP-1022 SKAMPI deployed using helm chart repo and umbrella chart (ADR-5)
- Discarded
- relates to
-
SS-47 MVP subsystems as self standing separable charts
- Done
-
SP-1241 Define the architecture of helm subcharts and repositories
- Done
- split to
-
ADR-24 Continuous Integration and Release pipelines
- Discarded
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- Wiki Page
-
Wiki Page Loading...