[Change]: Clarify 2.4.5

[rmbaxter67]

Summary

I'm struggling to understand what 2.4.5 means.

Source

No response

Detail

Para 2.4.5 currently says: "You must be able to replace a non-compliant TRE with a compliant system." This makes a sort-of sense (to me) for something like a pop-up TRE or a "fully Terraformed" TRE but I struggle to map it the bigger on-prem versions I know of. Also, a spec requirement that says "if your TRE isn't compliant [with this spec?] then you need to replace it with one that is" sits at odds with the fundamental premise of the spec that, if your enviornment isn't compliant with this spec then it's not actually a TRE. The ideas from 17/08/23's Collaboration Cafe on re-using and expanding the Turing paper on "what is a TRE?" as an intro and frame for this spec might help here.

Where

Para 2.4.5

Proposal

Maybe discussion needed on what this para is intending?

Who can help

No response

[JimMadge]

Good point.

My reading of that is that it relates to 2.4. Configuration management. That is, non-compliant means it doesn't match what your configuration management says it should be. I think it doesn't mean you need to be able to identify/replace any part of the infrastructure which is not SATRE compliant.

[rmbaxter67]

Ah, thanks Jim, that helps. I don't think I know enough about automated configuration to attempt a re-wording along the right lines, but "live environment not matching what the config says it ought to be" would be a useful clarification.