Introduction of Gateway in read-only mode
The Gateway 25.3 release introduces the ability to enable Gateway in read-only mode, allowing it to operate in a read-only state. When enabled, Gateway connects to Secondary or Tertiary Address Manager servers and only uses read-only sessions when authenticating with Address Manager, ensuring that no write operations or configuration changes are made.
Enabling Gateway in read-only mode allows you to offload reporting, analytics, and inventory workflows that only make use of read-only BAM APIs to this Gateway instance that authenticates against a Secondary or Tertiary Address Manager. This reduces the load on Primary Address Manager servers and minimizes performance impact in active environments.
Gateway containers fail to restart after changes are made in the Gateway UI
-e <bam_IP>
environment variable, making updates in the Gateway UI that would trigger an
update to the conf.py file, such as changing the logging
level, would result in Gateway adding an additional api_url
to the configuration. When attempting to restart Gateway, this additional
api_url resulted in the Gateway container failing to
start with the following error
message:ERROR: Address Manager alias '{ip/fqdn}' has already been defined in the configuration file.This issue has now been resolved.