mock-service | 入门级mock服务器 | Runtime Evironment library

Although GKE comes pre-configured to pull from registries within the same project, Kubernetes clusters generally require special configuration at the pod level to pull from private registries. It's a bit involved.

Fortunately minikube introduced a registry-creds add-on that will configure the minikube instance with appropriate credentials to pull images.

You will have to configure the interactions.url helper. See documentation for more details.

Later on you will have to build your own end-user interactions and with it you will have to configure this helper anyway.

Since you have targetPort: 8500 in the service the container inside the pod need to listen on port 8500.

The label in service is mock-service: test but in pod mock-services: true. They need to match.

Create a resource folder and place yaml file in that, don't place in target folder path because target folder always gets refreshed when ever build happens this makes file to be unavailable.

So please create separate resource folder and keep yaml file, then try accessing

Localhost inside your spring container, is your spring container. Instead of setting the host to localhost for your MQ Connection you need your container's / host ip.

How you do it depends on your host's platform, but it will be something like host.docker.internal

Your copied array might have a different reference, but the article objects inside each array is still the same. The copied array is not really necessary. At least not with your current requirements. What you need to do, is create a copy of the article itself:

Pact is telling you that the interaction never got triggered. You never call GET /posts/1 on the pact mock server, hence when you try to verify it, it'll say that it's missing the interaction and not product a pact file since it failed.

Unless https://jsonplaceholder.typicode.com/posts/1 points to the pact mock service (which I'm guessing it's not), this won't work. Whatever the port it's on (it's normally on localhost:), is what you need to hit.

Instead of the code you did, get the base URI from pact itself:

Not sure if this will be helpful or not, but I will post this as an answer in case it is, unfortunately I don't have a way of testing this myself.

I would approach this by trying to mock the TranslateService in your providers array with a mock. Perhaps something like this (but mock all the methods needed):

The code is failing because it's missing pact-web. You can see this in the error message you included: