Amplify-cli: amplify mock not working

Created on 20 May 2020 · 11Comments · Source: aws-amplify/amplify-cli

Note: If your question is regarding the AWS Amplify Console service, please log it in the
official AWS Amplify Console forum

Which Category is your question related to?
Mocking and Testing

Amplify CLI Version
4.20.0

What AWS Services are you utilizing?
Graphql, Elasticsearch (via @searchable)

Provide additional details e.g. code snippets
amplify mock

amplify mock fails

Mock does not handle CloudFormation resource of type AWS::Elasticsearch::Domain. Skipping processing resource ElasticSearchDomain.
Data source of type AMAZON_ELASTICSEARCH is not supported by local mocking. A NONE data source will be used.
Failed to start API Mock endpoint Error: Could not get resource ElasticSearchDomain

How can I bypass this?

Thanks

@searchable enhancement mock

Source

vasujogani

👍9 👀1

Most helpful comment

+1 Commenting out searchable is not a great answer.

TheBox193 on 9 Jun 2020

👍15

All 11 comments

Interested in this. I started getting 404 on a previously running react page yesterday.

weisisheng on 20 May 2020

@SwaySway any way to temporarily bypass this for now?

vasujogani on 22 May 2020

The CLI does not support mocking of searchable.
A potential workaround for this would be to comment out searchable before running amplify mock.
As a takeaway action we can look into how we can still provide mock functionality.

SwaySway on 23 May 2020

👍5

+1 Commenting out searchable is not a great answer.

TheBox193 on 9 Jun 2020

👍15

dtelaroli on 17 Jun 2020

The CLI does not support mocking of searchable.
A potential workaround for this would be to comment out searchable before running amplify mock.
As a takeaway action we can look into how we can still provide mock functionality.
@SwaySway
Why did the amplify cli regress on this? version 4.12.0 of the amplify cli supports mocking ElasticSearchDomain.

chrisw-asu on 6 Jul 2020

It is totally not cool to break old functionality in your product when releasing new versions of it. This should really eliminate amplify cli from being considered for any applications uses.

chrisw-asu on 6 Jul 2020

Mocking of APIs breaks out of the box for the Todo app. Mocking of Lambdas breaks out of the box on the Hello World function. Does anyone even build this?

seanchatman on 20 Jul 2020

mikerudge on 22 Jul 2020

👍3

+1 Any word on this? I'd really like to be able to launch graphiQL for the bulk of my local testing even if I have to stay away from search-related resolvers. Until then, I'm relegated to e2e testing direct with backend.