Currently, after building a DMS config and deploying it, if the user re-runs "config build" or wants to update a config, all questions are asked again.
However, some questions do NOT make sense to ask/capture again in an update/re-run use case. For example, re-entering the Ego client ID will generate a new secret and then cause conflicts with the existing secret and crash the script.
So for the update use case, we need to identify and hide questions that should not be asked (should just re-use existing/current value).
Currently, after building a DMS config and deploying it, if the user re-runs "config build" or wants to update a config, all questions are asked again.
However, some questions do NOT make sense to ask/capture again in an update/re-run use case. For example, re-entering the Ego client ID will generate a new secret and then cause conflicts with the existing secret and crash the script.
So for the update use case, we need to identify and hide questions that should not be asked (should just re-use existing/current value).
<TBD - Which inputs to skip/hide>