-
-
Notifications
You must be signed in to change notification settings - Fork 198
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
Add dispatching based on headers #549
Comments
@lbroudoux would this be something for a contribution? If yes, can you point me into the right direction? :) |
Hi @imod! This could be a great contribution! Definitely. I'll try to give you some hints for bootstrapping it. Basically, you'll have to consider 2 things:
Importer partThe main interface here is One important thing to notice is that during import you have to find Mock engine partNow the second part is to implement actual routing for incoming requests on mocks. This has to be done into the Hope it helps. Do not hesitate for further assistance. |
Hey @imod! Is it still something you're considering for a contribution? |
I would love to do so yes, but I just did not find the time yet - if your faster then I am, please feel free :) |
Thanks for quick reply. Dispatcher do not have to be implemented for all protocols. Regarding headers, I don't know if they make sense in the case of Soap of GraphQL... You can start with just one REST implementation and then we'll see 😉 |
Hey @imod! How are you doing? |
Hi @imod! We're shifting this one for other priorities. Is this something still of interest to you? |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. Microcks is a Cloud Native Computing Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
In my experience, most of the APIs do provide a way to retrieve a collection of items - even if I create a dynamic mock with microcks, i get an endpoint to collect all saved items. These endpoints mostly don't have any changing part in the URI.
If these items are not globally available for e.g. all user or depend on any other input passed with a header information, then I'm out of luck.
Common scenarios I see:
Sure in many cases the user is passed as a JWT, but not always.
In these cases the headers are the only arguments to get the relevant information and I think this should be made as easy as possible - specially as it is so simple to define these in e.g. the postman collection and import them.
The text was updated successfully, but these errors were encountered: