In test-suites, In multiple scenarios, we are reading data and writing them from and to the config file. In which, multiple services have an attribute ipv-4-address (either tcp-client or tcp-server) which will be parsed from chosen object. In v1.0.0, ipv-4-address is only attribute present in tcp-server or tcp-client instances to depict address on which an application is hosted, but in v2.0.0, it is added with domain-name attribute. So, the path needs to be updated wherever applicable
In test-suites, In multiple scenarios, we are reading data and writing them from and to the config file. In which, multiple services have an attribute ipv-4-address (either tcp-client or tcp-server) which will be parsed from chosen object. In v1.0.0, ipv-4-address is only attribute present in tcp-server or tcp-client instances to depict address on which an application is hosted, but in v2.0.0, it is added with domain-name attribute. So, the path needs to be updated wherever applicable