manage-additional-server-config.xml can be cached and not-templated on future runs

[faangbait]

Collection version

latest

Environment information

n/a

What happened?

On each of JMSTEST and JMSNEW, we provision a blank cluster, then install Core and Manage. On JMSTEST, we set the MAS Workspace ID to "test." On JMSNEW, we set the MAS Workspace ID to "new."

Expected behavior would be to retemplate this file, since a critical variable (e.g. in this case, the endpoint for the jms service) has changed. However, no replacements are made.

The result is the second cluster (workspace id "new") tries to connect to jms-test instead of jms-new

Relevant log output

See screenshot.