Open
Description
Please select the type of request
Enhancement
Tell us more
Describe the request
- deploy a app via appmanagement
- app gets deployed correctly to either a local scope or a cluster scope (cm, or shc deployer) directory
- remove/change application on disk for whatever reason (exception not on shc node or idx directly as the operator dont push directly and apps on shc are running with the shc deployer logic which allow files to change on sh , especially in local)
- observe
Expected behavior
- Operator detect app hash changed and redeploy it
but what happen now is
- nothing
which lead to a difference between what the user thing is deployed and reality (and is not aligned with helm+ operator idea)
I think we should just consider app pushed via s3 as immutable so operator would detect and fix in case files are changed
it could be disabled via a setting
Obvioulsy there is a risk that if app dev include a setting that will get obfuscated by splunk, this defacto will change file on disk and hash which could lead to a endless app installation loop (which is why it should be clearly documented as such and allow to disable the logic just in case)