Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different versions of same artifact are not exposed through stub runner. #474

Closed
mhmohapatra opened this issue Nov 29, 2017 · 2 comments
Labels
Milestone

Comments

@mhmohapatra
Copy link

@mhmohapatra mhmohapatra commented Nov 29, 2017

stubrunner:
ids:

  • "yyy:sample-service:1.0.0:stubs:9898"
  • "yyy:sample-service:2.0.0:stubs:9899"

In this instance version 1.0.0 is exposed at port 9899 which is assigned to version 2.0.0.

//cc @bijukunjummen

@marcingrzejszczak

This comment has been minimized.

Copy link
Contributor

@marcingrzejszczak marcingrzejszczak commented Nov 29, 2017

Most likely I have a set somewhere and a lookup via group id and artifact id. What's the usecase of having 2 stubs at the same time?

Of course the workaround would be to run 2 separate tests, right?

@bijukunjummen

This comment has been minimized.

Copy link
Contributor

@bijukunjummen bijukunjummen commented Nov 29, 2017

Hey @marcingrzejszczak,
@mhmohapatra and I were working on a sample when we saw this issue.

We are working on a team which manages a set of microservices, so we have created this centralized stub server portal(using @EnableStubServerRunner) with the stubs hosted as wiremock servers. We just wanted to see what the behavior will be if there were two different versions of a microservice stub hosted on the stub server and saw this issue.

So this issue is not in a test, but when hosting the stub in a stub server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.