Whilst doing regression on API imports across versions, some issues were detected that need to be fixed in order to validate ticket #7807
3.15
for every API import done there is an error displayed but the import is still done and the api gets created/updated
when importing an API definition (with no plans) to update an existing API (that has a plan) the update does not delete the existing plan - this is the expected behaviour mentioned on #7807
when importing an API definition (with multiple roles) to update/create an API the update does add the multiple roles to the API definition - this is the expected behaviour mentioned on #7807
3.17
when importing an API definition (with no plans) to update an existing API (that has a plan) the update does not delete the existing plan - this is the expected behaviour mentioned on #7807
when importing an API definition (with multiple roles) to update/create an API the update does add the multiple roles to the API definition - this is the expected behaviour mentioned on #7807
The behaviours mentioned above were verified on each respective envir for APIM 3.15 and 3.17
Whilst doing regression on API imports across versions, some issues were detected that need to be fixed in order to validate ticket #7807
3.15
3.17
The behaviours mentioned above were verified on each respective envir for APIM 3.15 and 3.17