ol-infrastructure
ol-infrastructure copied to clipboard
Architecture documentation
wrt: duplicating configuration items, particularly between infrastructure stacks and substructure stacks. Could use an outline / guide on what goes in an substructure and what goes in an infrastructure stack and how to best share items between the two.
This sounds like an opportunity for me to write up some design/architecture documentation about the overall project structure, as well as some import linting to help enforce some of that, though this sounds like an example that wouldn't be easily caught by linting.
and
I agree that stack references are a great way to show the dependency chain and avoid configuration drift
additionally:
mike: I think the only reservation I have about stackrefs is that they would (possibly) cause confusion/problems in a hypothetical “everything is gone we need to start over from scratch!” situation because they have the possibility of introducing cyclic dependencies if they evolve over time but, like, that isn’t necessarily real-world
tmacey: That is something we should be able to write a linting rule for. Please add that to wherever you're capturing this issue.