Ole Lensmar
Ole Lensmar
I'm fine with us just doing this for one gateway to start with - as a PoC - whichever one is easiest!
@aabedraba how is this different from the x-kusk cors extension?
Perhaps we can start with the scenario where Kong already exists in your cluster (which to me seems more likely than that you would explicitly want to use Kong instead...
great idea! - we discussed this initially but were worried that there could be CORS issues when trying to request an openapi definition from an arbitrary URL - but that...
good point @aabedraba - the initial idea of this functionality was to make it easy for users to "try out" KGW with an existing OpenAPI definition - you're totally right...
duh - why didn't I think of that! We should definitely be able to auto-generate some of these (methods, hosts, headers) - perhaps this could be a `template: auto` setting!?
thanks @Tarick - @kdhamric please add anything there that might be relevant/related to OT...
afaik - we aren't using the official Choco repo because of the 3-4 week delays when publishing new releases - for our own repo I think we need to extract...
We already scrape Helm Charts and Docker image downloads from DockerHub - the later are not very helpful since those images can be pulled from anywhere - not just Helm...
Thanks @sharmajee1 - would this apply to arbitrary test artifacts also? (log files, videos, etc)