Problem:
There are KB articles that provide solutions based on modifications of files managed by the installer. All these changes will get lost if the installer is executed again. The main reason to do this is because rerun the installer might be a heavy and time consuming operation and customers prefer a simple way to fix it, but it is inconsistent and the KB must warn about the risk to lose the change. 

Since the installer is the only supported way to manage the installation of AAP it would be good if it support options to apply lightweight changes. The combination of tags in the ansible-collection plus some flag or option in the setup.sh could enable this behavior. 

Example: 

If the customer wants to change the automationedacontroller_allowed_hostnames, the operation should be fast since it only requires re-template a couple of files and restart a couple of services. 

This kind of tasks could be identified and marked with a tag like for example apply-config, in that way rerun the installer would take much less time.