If you start a 4.2 process with the following in the config file:

 ssl:
    CAFile: /tmp/mms-automation/test/output/certificates/mmsCA.pem
    PEMKeyFile: /tmp/mms-automation/test/output/certificates/cert-763911616
    clusterFile: /tmp/mms-automation/test/output/certificates/cert-827743263
    mode: requireSSL

When you run getCmdLineOpts, you get the following:

tls: {
  certificateKeyFile:/tmp/mms-automation/test/output/certificates/cert-991138764, 
  clusterFile:/tmp/mms-automation/test/output/certificates/cert-391280315, 
  CAFile:/tmp/mms-automation/test/output/certificates/mmsCA.pem
}, 
ssl: {
  mode:requireSSL
}

The fact that the ssl arguments are translated at all is unexpected – the server hasn't done that for other deprecated args.

Automation cares about this because we run getCmdLineOpts to check that the process is running with the correct process arguments.

Our preference here would be that the server translates none of the arguments – that getCmdLineOpts returns what the user actually started with in the conf file. If that's not possible, to translate all of the arguments, and not leave the dangling "ssl" in a case like this.

Thank you!
(spoke to spencer.jackson who recommended filing a ticket)