Laurent Broudoux

I spent some time yesterday on this, and I got it working, and I needed to do some refactoring. The trickiest thing I didn't notice before was that the watcher...

Working fine! This is the scenario I have tested: 1. Launch a regular Microcks instance: `docker run -p 8585:8080 -p 8686:9090 -it --rm quay.io/microcks/microcks-uber:nightly-native` 2. Issue the `import` command with...

Just a small addition here: the Microcks' ruleset just uses the Spectral's `oas3-valid-media-example` with no modification. So the question relates to how this rule is doing validation.

Hi @karthikrajkkr This is a super interesting configuration. I think what you observe is due to the sampling setting of our OLTP tracing part. The default setting is as follows:...

Hey @karthikrajkkr and @Apoorva64 I apologize for my previous response, which I think I addressed too quickly. Thanks, @Apoorva64, for providing the correct answer. I think that what you're suggesting...

Thinking about it ... another way to work around this - **if the Microcks instances are running on the developer's machines** - is to have session stickiness enabled at the...

It's just that the `--microcksURL` flag no longer requires the `/api` suffix. Change the value to `https://microcks.127.0.0.1.nip.io` and it should work. However, I agree that we may add an extra...

Nope. I think we screwed things a bit during the latest release...

Hey @dontfreakout Thanks for your patience. This is a nice suggestion! I would keep Redocly as the default as of now, as it seems more popular (until now) in the...

Yes, please do so! 🚀 Ideally, you would also include the settings in the Helm chart to allow setting the new dedicated feature property ;-)