Multiple SSH key definition based on AWS region for Geo deployment

• GET version: 2.8.5
• Cloud Provider: AWS Multi Region/VPC/Account
• Environment configuration: 10k HA Hybrid

Not sure this is a "bug" or necessarily a feature request.

Customer has primary in us-east-1, and secondary in eu-north-1, both using different ssh keys. When attempting to run the gitlab_geo.yml playbook where they provide both inventory files, the "merged" vars take the secondary's ssh key value and override it for the primary.

How can we supply different values for the same variable and have it "stick" when running the above playbook?

Please let me know if I need to adjust this issues definition, labels or provide more context/output etc.