You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixes atrt custom processes port arguments/configuration generation by
attempting to load them before generation.
When using config.ini files, user is expected to manually configure all
settings for all processes. For custom processes, specifying port
settings had no effect and ATRT was automatically generating ports.
Added logic to ensure that when port options are specified, those are
loaded and the values used when generating command line arguments.
atrt current implementation is a bit strict. Code was already available
to load and generation options for processes, but only if those options
are mandatory.
In case of custom processes, port options is configured via
[cluster_deployment] generate-port setting, which doesn't exactly fit
how atrt has been implemented.
Required changes were:
* when loading a custom process, load any setting that has been
specified in it's own configuration group
* enable f_options "--port" configuration for custom processes
* disable custom processes from pr_proc_options logic (which
automatically generates --port settings if missing)
* disable custom processes from pr_proc_check logic (which enforces
the existence of all settings configured in f_options).
* modified logic in load_deployment_options_for_process to skip
settings port generation if port has been configured.
* fix logic to generate custom processes CONNECTSTRING environment
variable to add port number in case port has been loaded (higher
precedence) or generated (lower precedence).
0 commit comments