BrokerProxy - getRegistryPropertyNames does not give back mqKeyRepository

Idea / RFE Review. Thank you for taking the time to raise this enhancement request. The ACE admin API (described by our Open API v3 document which is available on the URL route /apidocs from any started integration node or server) gives dynamic access to a wide variety of the most commonly used integration node properties. However, as noted, in ACEv11 and ACEv12, the code is very specific in this area and only picks out certain properties for return across the admin REST API and unfortunately mqKeyRepository is one of those not currently exposed. As you may have noticed, some properties, such as those associated with the "BrokerRegistry" component of the integration node, of which mqKeyRepository is one example, currently require an integration node restart to become effective. Properties of this sort can still be editted using the mqsichangeproperties command, which you will then see evidence of the change in the override node.conf.yaml file, but the node must be restarted for them to become effective. Similarly, a locally executed mqsireportproperties command can report on the BrokerRegistry directly... but when considering remote access, one thing we would need to consider is whether absolute paths to security aspects may not be suitable for exposure over remote connections. We are updating the status of the idea to Future Consideration and invite comments from the community about whether this property should be considered suitable for remote reporting.