Description:
When using APIM as the CP for the APK via agent, after redeploying an API(with resource level interceptors) after adding a new resource from the APIM make the resource level interceptors stop working. The observation was, after adding adding and deploying the API with the new resource, in CR updating/creation process the data related to interceptors gets removed from the API PolicyCR. However the agent generates the proper APK-Conf for that scenario, config-ds returns the CRs without attaching the interceptor details in the APIPolicyCR. This issue occurs only when there are multiple resources for an API.
Steps to reproduce:
From the APIM, Create an API and add resource level interceptors for an endpoint.
Try to invoke that endpoint and the interceptor should properly work.
Go to API Configurations > Resources and add a new resource and redeploy the new revision.
Again try to invoke the same endpoint and now the interceptor won't work as intended.
Description: When using APIM as the CP for the APK via agent, after redeploying an API(with resource level interceptors) after adding a new resource from the APIM make the resource level interceptors stop working. The observation was, after adding adding and deploying the API with the new resource, in CR updating/creation process the data related to interceptors gets removed from the API PolicyCR. However the agent generates the proper APK-Conf for that scenario, config-ds returns the CRs without attaching the interceptor details in the APIPolicyCR. This issue occurs only when there are multiple resources for an API.
Steps to reproduce: