Bug Report

System Information

• Any
• 2.4.4.0
• Mainline

I confirm:

• [x] that I have searched for an existing bug report for this issue.
• [x] that I am using the latest available version of AMP.
• [x] that my operating system is up-to-date.

Symptoms

• What are you trying to do?

  Either:

  • Refresh Configuration from the controller on an instance that is installed on a target, to update the instance to the latest generic template config; or
  • Fetch Latest on the controller to create a new instance on a target (from the controller) based on the latest generic template config.

• What are you expecting to happen?

  The existing instance will be updated to the latest generic template config, or the new instance will be created based on the latest generic template config.

• What is actually happening? ('Nothing' is not an acceptable answer!)

  The target ADS is not updated to the latest generic template configs. Only the controller ADS is. As a result, the existing instance is not updated correctly, and a new instance is not created with the latest config. This causes breakages and/or unexpected behaviour of the instance.

  What should happen is that if a Fetch Latest or Refresh Configuration happens on a controller, that should automatically also be done on the target(s), so that any instances are updated/created correctly on the target(s).

Reproduction

See above.

Putting a note here to check into this. The latest version should sync the fetching, but I had one case where the settings file and kvp weren't matched up properly when using a duplicated game that existed in the main repo and Greelan's dev repo. Need to verify further it wasn't an unrelated fluke.

Turns out, adding a repo on the controller does indeed add it/refresh it on the targets... It just doesn't refresh on the controller.

O.M.G.