Update kube schema url to v1.14.0

[jburianek]

This seems to fix #58 for me.

Is the fix that straightforward, or is there something I'm missing? Thanks!

[JPinkney]

Does autocompletion still work on kind/apiVersion also validation? The problem is that the official schema has this "x-kubernetes-group-version-kind" field in that holds different apiVersion, kind, and group they can be associated with e.g. https://github.com/garethr/kubernetes-json-schema/blob/master/v1.9.9-local/_definitions.json#L24. The problem with this is that it isn't supported by json schema spec and when I was trying to get it to work in the parser I ran into some issue (I cannot remember what the issue was) that made it so you had to transform the schema. IIRC I have a python script somewhere that basically took the "x-kubernetes-group-version-kind" and put it inside of the properties field in a different format that made the schema work correctly. Thats why there is the patched schema in there.

Here is an example of what had to be done. apiVersion became its own field inside of properties with type string and enum v1 (basically the transformed version of x-kubernetes-group-version-kind below).

[jburianek]

Ah ok, that makes sense. You're right, that does break autocompletion for apiVersion/kind. I knew I had to be missing something 😃

[jburianek]

I'd be interested in that script if you can find it. Might be worthwhile to commit it to source somewhere too.

[JPinkney]

I'll try to look for it but if I can't I'll have to wait until after my exams and I'll create a repo or a gist of the code

[coveralls]

Coverage remained the same at 71.855% when pulling a3cf2fc on jburianek:update-kube-schema into 7bbcf2f on redhat-developer:master.

[pengx17]

IIRC I have a python script somewhere that basically took the "x-kubernetes-group-version-kind" and put it inside of the properties field in a different format that made the schema work correctly. Thats why there is the patched schema in there.

@JPinkney I am also interested in the script you mentioned here. And good luck to your exams :D

[JPinkney]

@pengx17 I couldn't find the script and was going to write a new one but it looks like @jburianek already has a PR open on the schema side for all the fixes (garethr/kubernetes-json-schema#16).

Awesome work @jburianek !

[jburianek]

Things have been fixed upstream, so I've updated this PR to point to the JSON schema that should resolve this.

[jburianek]

@JPinkney Now that the schema side has been fixed, any chance we could merge this to pick up the latest schema?

[JPinkney]

@jburianek Have you played around with it to make sure everything is okay? (I haven't checked it out yet so I was just wondering if there were any other issues found). If we can't find anything I'll try and cut a release near the end of this week with it in it!

[jburianek]

@JPinkney Thanks, yeah I've played around with it and things seem to work as expected.

Before:

After: