Andrey Vazhenin commented on AMBARI-25503:
> I don't think that it is a good idea to manage it as an text file.
I agree that it's not a good idea, but in most cases it's the simplest and the
fastest way to handle.
> which should be ignored by any CMS, which understand the file format
Yes, it can be ignored, but the provided information:
a. duplicates with the system, e.g. the access time or process up time can
answer when the app was started and last configuraition were modified
b. the checksum of the file changes every time the application restarts
c. the modification time changes every time the application restarts
d. In some security reasons, It would be better if the application requires
read-only access to the configuration files.
This list can be longer, but still I don't understand the purpose of doing such
thing like give an opportunity to the application to manage it's own
configuration that controls the application.
> Ambari always rewrite the properties at startup
> Key: AMBARI-25503
> URL: https://issues.apache.org/jira/browse/AMBARI-25503
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.5
>Reporter: Andrey Vazhenin
> The ambari.properties file is always saves by the ambari-server process at
> startup and saves the timestamp at the file, so any configuration management
> systems can't manage this file.
> [Save the timestamp
This message was sent by Atlassian Jira