Utility outputs 'API not found' even if it does exist

[andreachild]

The utility can sometimes error saying 'API not found' even if the app sync API does exist in AWS when attempting to update an existing app sync API.

Example of input args:

--input-graphdb-schema-neptune-endpoint 1234567890.us-west-2.neptune.amazonaws.com:8182 --create-update-aws-pipeline --create-update-aws-pipeline-name 1234567890 --output-resolver-query-https --log-verbose

Example output:

Creating or updating AWS pipeline resources ...
Checking pipeline resources
√ Found lambda
‼ API not found
√ Lambda execution role found
Pipeline does not exist.
One or more pipeline resources are missing.
AppSync 1234567890API is  missing.
Fix the issue manually or create the pipeline resources with a new name.

The problem is the usage of ListGraphqlApisCommand to determine if the API exists in pipelineResources.js - this command has a maxResults arg which is not being set and the default is something like 10 results. If there are more than 10 app sync APIs then it is possible the utility will think the API does not exist.