API-Mgr. CLI version
1.3.12
API-Manager and Service-Pack Version
7.7.20210530
Expected behavior
When an API has been imported, granting applications access to it, should not fail.
Actual behavior
Even if the Front-End API has just being created, the API-Manager complains it cannot find the entity. This is very similar to issue: #212 which has been solved by #213.
But in this case, the API-Manager returns: The entity could not be found. instead of Unknown API and therefore the APIM-CLI does not retry.
Also in this case, the APIM-CLI should retry granting access to the API in the same way.
Log-Output in Debug
17189 INFO APIImportManager| Update API Strategy: Re-Create API as changes can't be applied to existing API.
17189 DEBUG APIImportManager| Apply breaking changes: [apiDefinition, securityProfiles, outboundProfiles] & and Non-Breaking: [clientOrganizations, customProperties], for PU BLISHED
17190 INFO RecreateToUpdateAPI| Create new API to update existing: 'ABCD - Chorus Pro - Utilisateurs' (ID: 4560af15-abec-4ccc-984d-276d7cb83c06)
17191 DEBUG APIManagerAPIAdapter| Import backend API: ABCD - Chorus Pro - Utilisateurs based on Swagger 2.0 specification.
17316 INFO CreateNewAPI| Create published API: 'ABCD - Chorus Pro - Utilisateurs' 1.0.0 based on Swagger 2.0 specification.
17316 DEBUG APIManagerAPIAdapter| Create Front-End API: 'ABCD - Chorus Pro - Utilisateurs' (API-Proxy)
17381 DEBUG APIManagerAPIAdapter| Updating API-Proxy
17476 DEBUG APIManagerAPIAdapter| Updating API-Proxy-Image from file: Chorus-Pro.png
17575 DEBUG APIStatusManager| Updating API-Status from: 'unpublished' to 'published'
17576 DEBUG APIManagerAPIAdapter| Update API-Proxy status to: published
17644 DEBUG APIManagerAPIAdapter| Upgrade access & subscriptions to API: ABCD - Chorus Pro - Utilisateurs 1.0.0(1d6b2640-aae3-492a-a685-59653177578c)
26927 ERROR APIManagerAPIAdapter| Error upgrading access to newer API. Received Status-Code: 404, Response: {"errors":[{"code":102,"message":"The entity could not be found. Please refresh your session."}]}
API-Mgr. CLI version
1.3.12
API-Manager and Service-Pack Version
7.7.20210530
Expected behavior
When an API has been imported, granting applications access to it, should not fail.
Actual behavior
Even if the Front-End API has just being created, the API-Manager complains it cannot find the entity. This is very similar to issue: #212 which has been solved by #213.
But in this case, the API-Manager returns:
The entity could not be found.instead ofUnknown APIand therefore the APIM-CLI does not retry.Also in this case, the APIM-CLI should retry granting access to the API in the same way.
Log-Output in Debug