-
Notifications
You must be signed in to change notification settings - Fork 858
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
Fix documentation where schematic for component definition refers to kube #6436
Comments
Hey, @anoop2811 ! I would like to give it a try. |
Hey @professorabhay ! Welcome to the community. One way you could do is search in the code under the docs directory for "kube:" and look for occurrences under schematic, convert them to using cue and test the same locally. You can refer to an example here: https://kubevela.io/docs/platform-engineers/oam/x-definition/#specpoddisruptive. Let us know if you need any further help. |
Ok @anoop2811, I got it almost. Just one question - 1 - 2 - In both files *both are same |
@professorabhay you would need to change it to cue and the template needs to be converted from yaml to cuelang equivalent for that yaml |
Hi @anoop2811 I have opened a PR, can you please take a look at it? Thanks |
Refer to this slack conversation: https://cloud-native.slack.com/archives/C01BLQ3HTJA/p1704394842494259
The kube scematic was deprecated in this commit: f1bae16
However we still have documentation like here where it refers to kube schematic. We should update this to using cue.
The text was updated successfully, but these errors were encountered: