We have a test VC server, that jobs are created on, and then copied into production. The test server contains many of the same connections and PGP keys as the production servers, but it is not kept perfectly synchronized, since it does not concurrently run all of the jobs that are on a production server.
When I copied a job from the test server to a production server, I also wanted to export the PGP key and connection for it, and import it into the production server. I used VC client 4.9.40 - the production and test servers are running 4.9.26. When I did the export from the test server, I selected one specific PGP key and one specific connection to export - then imported that into the production server, and selected "update existing". The expected result was that it should have had no impact on anything else - it should only have added one PGP key and one connection to the production server that I wanted to use in the job I copied over from the test server.
However, today, some of our production jobs failed - some connections and PGP keys were changed or missing that were unrelated to the one of interest. Since the PGP keys and connections are not perfectly synchronized between the test and production servers, it appears that it may have changed other PGP keys and connections that were not the same between the two servers. Since I had made a specific selection of a particular PGP key and connection during the export, this was unexpected.
Looking at the export xml file now, it appears that for the PGP keys, even when a specific key is selected, it looks like it will export the entire keyring? And for the connections, it looks like it exports all of them even if one is selected?