Re: Additional .ini file

On 23/12/2022 11.29, Custom Log wrote:

> But I wonder if it is a correct practice, given that /etc is a system 
> directory (which contains system configuration files), and the system 
> directories should not be touched.

It's just bogus, this are configuration files which the administrator of 
the system should tweak so that the machine is doing what the 
administrator needs it to be able to do.

Just avoid making things writeable by everyone or files with passwords 
or private keys readable by anyone.


> Would it therefore be advisable to specify (through the 
> chef_ini_scan_dir) environment variable) an alternative directory?

No, this could lead to that you don't find the file that easily or in 
worst case the file is writeable for everyone, which could make your 
system easier to be compromised.


 > However, a possible update (of the system) could lead to the overwriting
 > of some of these files

Most package managers do be able to detect if a file is modified and 
then just saves the new config with a postfix. If you create a new file, 
the package manager will know it and will not be trying to save over it 
unless the package for some reason would include a new config file named 
the same as your "random name", but then it would just add a postfix to 
the config file from the package.


-- 

  //Aho