Well the use case is that a specific resource bundle had been created by hand through the CMS content perspective which we use to hold configuration values for logic used elsewhere in the system. We are not using it truely for “messages” as resource bundles were originally intended but more of an adhoc key/value store. Normally when we have new configuration key/value pair combinations that we need to deploy we just do these by hand for the initial default values but having to do this in several staging environments as well as production by hand becomes tedious so we figured we’d look into what mechanisms we have available for either adding key/value pairs to existing resource bundles or less desirably replacing the content of a single resource bundle at deployment time through the bootstrapping process.
So far, going the route of separating the single resource bundle into it’s own “base-node” / “content source” based on the auto export documentation on Dynamic Resource Bundle Node Structure (we are actually using v13) and using hcm-actions.yaml to reload the specific content path to our resource bundle we have yet to get this to work. I’m suspecting that the issue may just be related to the several other bootstrapping errors that we have become accustomed to ignoring over the last few years as nobody really understood the significance. It looks like to me now that we may have attempts to update configuration values which are not “categorized as content” in previous version sections in hcm-actions.yaml which I’m guessing may be contributing to other parts of the bootstrapping from being skipped. One thing that I’m trying to sort out right now is whether it’s actually expected or supported to specify non-content node actions in hcm-actions.yaml since based on it’s location (not under the content subdirectory) and it’s name, it doesn’t appear to be meant to apply exclusively to content. In short, we may need to clean up and fix other bootstrapping problems before we can really tell whether we are doing this correctly or not.
On another note the ResourceBundleUpdater looks pretty interesting from our use case the comment on this other thread linked below.