add a check in common_services role in ansible-devops to check if v4 version of cpfs is already installed
if it is then skip common_services v3 install
this will add a safe guard on our side when we enable cpd 4.8
we don't want common_services role to run when v4 is already installed because if v3 is attempted to be installed in an env with v4 already installed, it will mess things up
Tests via mas install cmd in cli showing it is skipping the v3 install:
Ultimately it's easier to skip that directly in the ansible-devops rather than anticipate all possible conditions that we should cover to skip this in mas cli logic.
add a check in
common_services rolein ansible-devops to check if v4 version of cpfs is already installed if it is then skipcommon_servicesv3 install this will add a safe guard on our side when we enable cpd 4.8 we don't wantcommon_servicesrole to run when v4 is already installed because if v3 is attempted to be installed in an env with v4 already installed, it will mess things upTests via mas install cmd in cli showing it is skipping the v3 install:
Ultimately it's easier to skip that directly in the ansible-devops rather than anticipate all possible conditions that we should cover to skip this in mas cli logic.