Description of problem:
[RFE] Satellite-maintain should set read-only attribute, for important Satellite and Capsule configuration file
Version-Release number of selected component (if applicable):
Red Hat Satellite/Capsule 6.x
Satellite is based on puppet architecture, however a lot of customer uses their own config mgmt tools to manage configuration in their environment(ex. External puppet,Chef) and sometime just to test few settings, customer manually/using external configuration mgmt tools modify these important configuration files (Ex. satellite-answers.yaml/satellite.yaml), which does not impact the running satellite server, however during upgrade/update the Satellite-maintain/satellite-installer fails with sytax error and sometime it is difficult to recover as customer's are not fully aware of what changes were done and by whom.
To avoid such scenario, I have reported this RFE to address the issue. Where during installation, the satellite-installer will set read only attributes for important configuration file for existing satellite-server deployment, during upgrade the satellite-maintain should set the file-system attribute. Just like we have recently implemented the version lock feature for package update in satelite
For example we can use the chattr command to set and unset the attribute as an when required by the satellite-maintain.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support.
Thank you Sean