Will include that file in the set saved by the pre-uninstall script. Then will merge the packaged version & the saved version, and continue processing the upgrade.

Tested it in develop-1.1, ported it to -1.0 and develop. It's functional but writes a new mycnf-include-args.text file that looks like the following:
<comments from both, de-duplicated and alphabetized>
<options from both, de-duplicated and alphabetized>

If they had a comment associated with an entry, it will now be jumbled together at the top with the other comments. If anybody cares about that I can implement it differently.

To test...

Note, this mod includes a change to the pre-uninstall script, which older versions obviously won't have. It's a one line change, which makes a copy of your mycnf-include.text file so it doesn't get overwritten by the new installation. People upgrading TO this version will have to make the copy by hand. People upgrading FROM this option don't have to do anything.

1) Add an option to your mycnf file (it can be bogus b/c this test doesn't involve running columnstore). So BogusValue=1
2) Add the name of your value to the list at bin/myCnf-include.text
3) Copy your bin/myCnf-include.text file to bin/myCnf-include.text.rpmsave
4) Run the upgrade like usual.
5) Look at your myCnf-include.text file and myCnf.cnf file, and see that your new value is still in both.

QA task for 1.1.7 and 1.0.16 has been moved to a new ticket MCOL-1974

Build verified: 1.2.2-1

Tests performed:

1) Centos 7
2) RPM and binary
3) single server, multiple server
4) localquery and non-localquery
5) upgrade from prior releases and from 1.2.2-1 forward by "upgrading" to 1.2.2-1

All in all, it is working as expected.
There is also a myCnf-exclude-args.text file in the MCS bin directory, but it is not being used. I suggest that we should have the exclude functionality implemented or have the file removed to avoid confusion.

Note for localquery setup (1UM2PM)

The user only needs to setup the myCnf-include-args.text file on UM1. User customized values are being kept on UM1, and propagated to PMs.