Ádám Sándor

Separate repos for each sample or single samples repo? I'd vote for single samples repo, so when the framework changes we can upgrade the samples with one PR.

I think single repo for all (non-test) samples would be better. Easier to browse all the samples and easier to upgrade them on FW change.

I don't think memcached will be a production ready operator and it should actually go into the repo in the operator-sdk with the other memcached samples.

here https://github.com/operator-framework/operator-sdk-samples

@wtrocki please jump in our Discord channel (https://discord.gg/DacEhAy) you can find the invite as a pinned message in the general channel. You are very welcome to join the weeklys.

This is my proposal: .h4 java-operator-sdk/operator-framework/samples * basic sample with all features used in some contrived way .h4 java-operator-sdk/samples * spring-boot * quarkus * mysql-schema (demonstrating managing external resources) *...

Looks like this is already fixed just not released: https://github.com/open-policy-agent/opa-idea-plugin/commit/793e4e38123362888b26fab80b75bb556a1d26a6

I would really appreciate if this got implemented. It's the only reason I have to use VSCode sometimes :D