Update the auto YAML Generation #7725
Conversation
unsur eif schema./yaml is maintained or auto generated.
|
@mindspank thoughts on this PR?
If approved, ill go back in and overwrite /reference/project-files/ and fix any broken links |
|
@royendo , we prefer using a single file instead of using imports — like in this example, where everything is in one file. Initially, I had created separate files and imported them into project.schema.yaml, like you did, but @begelundmuller suggested keeping everything in one file. |
docs/docs/hidden/yaml/connectors.md
Outdated
|
|
||
| #### `aws_access_key_id` | ||
|
|
||
| _[string]_ - AWS Access Key ID used for authentication. Required when using static credentials directly or as base credentials for assuming a role. |
There was a problem hiding this comment.
I can see change difference in line spacing
Before Change
After Change
Properties and description is little congested.
all schemas into one including rillyaml. commented out lines. reworked generate-project.go: - moved out logic for sample in copy, uses schema sample instead - adding in line examples
next will be adding more examples
makes more sense, less duplicate info
confirm yaml, comment out sources
"/Users/royendo/Desktop/GitHub/rill/runtime/parser/schema/project.schema.yaml": [
"alerts/**/*.yaml",
"apis/**/*.yaml",
"connectors/**/*.yaml",
"dashboards/**/*.yaml",
"metrics/**/*.yaml",
"models/**/*.yaml",
// "sources/**/*.yaml"
]
}
…into docs/auto-gen-YAML
|
no rush but was able to fix the YAML thing we discussed by commenting out sources, and moved rillyaml out. i overwrote project-files/ and fixed links in 95319e0. should be good to go! |
Separated the schema files for easier management
referenced in project.schema.yaml.
reworked connections to look similar to currrent with copiable form.
models.schema.yaml --> advanced-model.schema.yaml
once confirmed, we can move this to rewrite /reference/project--files/
Checklist: