On Thursday, October 25, 2018 at 11:50:32 AM UTC-7, Wayne Johnston wrote:
Yes. But say I have 5 (ha!) applications loaded, and one of them is loaded by config map A, another is loaded by config map B, and all 5 are loaded by some real old version of config map C (and those config maps load nothing else in this example), then you'd have to list all 3 config maps as loaded, even if you didn't literally load any of them.
That is correct. Configuration Maps leave no artefacts of their own in the image. So all such a script can do is identify which Configuration Maps could have been loaded by you to produce the evidence found in the image. It cannot determine what actions you actually performed to produce that result. Likewise, if you loaded a Configuration Map and manually unloaded one application, the script could not determine that you had loaded that Configuration Map.
And if you have all applications loaded that a config map "D" loads, but the config map loads another config map "E" which isn't loaded, you couldn't list D.
There is nothing preventing the script from considering the required Configuration Maps in its determination. e.g. determine all possible Configuration Maps which could explain the loaded applications and then remove from the result any whose required maps are not also in that list. The latter is probably a recursive operation until there are no more being disqualified.
Note that one could also (unreliably, of course) scan the doit.log for evidence of which Configuration Maps were actually recorded as loaded.
--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[hidden email].
To post to this group, send email to
[hidden email].
Visit this group at
https://groups.google.com/group/va-smalltalk.
For more options, visit
https://groups.google.com/d/optout.
Locked
