BUG BUG: Stop putting dynamic data in AEX configuration file
We push all our systems configuration files out from a central repoistroy on our linux systems.
But the AEX client keeps CHANGING the file so our system keeps rechanging it back.
Someone decided it would be a good idea to keep some dynamic data in the CONFIGURATION file. Two timestamp variables are updated in the config file constanty by the client and that makes this suddenly a dyamic file that can't be centrally managed.
WHY would a developer not think maybe a timestamp would be a good thing to store in a different location than the place where the entire rest of the client configuration is stored??!