We are using GMU to export services which are using shared fragments and the result is one xml (--format singleFile) which include the service and shared fragments.
Is there any way that the xml should not contains the fragments that are used in API from other folders.
e.g. we have exported one folder(folder A) and it has 1 API and this API contains fragment for folder B.
Is it possible to avoid the entry/details of the fragment from the folder B in the xml generated.
Release : 9.2
Component : API GATEWAY
There is no option in GMU to exclude the included fragments when migrating Out a service.