Full Scope Required For Replacements Modification

[jeixav]

Do changes to "replacements" in config.json require running the state machine with input {"scope":"FULL","mode":"APPLY"}?

I changed "range-restrict" and "${RANGE-RESTRICT}" is referenced by a single account, one under "mandatory-account-configs". I thought I should therefore run the main state machine with input:

{"scope":"ACCOUNT","targetAccounts":[X],"mode":"APPLY"}

I used the actual account number instead of X, i.e. an 11 digit number as the first digit of the 12 digit account number is 0.

However the execution failed at Compare Configurations:

{
  "name": "Failed",
  "input": "{\"Error\":\"Error\",\"Cause\":\"{\\\"errorType\\\":\\\"Error\\\",\\\"errorMessage\\\":\\\"There were errors while comparing the configuration changes:\\\\nConfigCheck: blocked changing from config path \\\\\\\"replacements/range-restrict/2\\\\\\\" in SCOPE validation\\\\nConfigCheck: blocked changing from config path \\\\\\\"replacements/range-restrict/1\\\\\\\" in SCOPE validation\\\",\\\"trace\\\":[\\\"Error: There were errors while comparing the configuration changes:\\\",\\\"ConfigCheck: blocked changing from config path \\\\\\\"replacements/range-restrict/2\\\\\\\" in SCOPE validation\\\",\\\"ConfigCheck: blocked changing from config path \\\\\\\"replacements/range-restrict/1\\\\\\\" in SCOPE validation\\\",\\\"    at Runtime.d50 [as handler] (/var/task/index.js:1392:49382)\\\",\\\"    at processTicksAndRejections (internal/process/task_queues.js:95:5)\\\"]}\"}",
  "inputDetails": {
    "truncated": false
  }
}

Running the state machine with input {"scope":"FULL","mode":"APPLY"} succeeded.

The documentation states

All comparisons for config file changes are assessed AFTER all replacements have been made. Changing variable names which result in the same end outcome do NOT appear as a change to the config file.

I therefore expected {"scope":"ACCOUNT","targetAccounts":[X],"mode":"APPLY"} to work.