Jesús Pérez 9cef9b8d57 refactor: consolidate configuration directories
Merge _configs/ into config/ for single configuration directory.
Update all path references.

Changes:
- Move _configs/* to config/
- Update .gitignore for new patterns
- No code references to _configs/ found

Impact: -1 root directory (layout_conventions.md compliance)
2025-12-26 18:36:23 +00:00

44 lines
1.4 KiB
Markdown

# Syntaxis KCL Templates
This directory contains syntaxis-specific KCL templates that override the default provctl templates.
## Files
If you need to customize KCL generation for syntaxis-specific patterns, add these files:
- `schemas.k.j2` - Override default service/preset schemas with syntaxis-specific ones
- `defaults.k.j2` - Override default service instances (e.g., with syntaxis-specific configurations)
- `services.k.j2` - Override how services are assembled
- `presets.k.j2` - Override how presets are defined
- `deployment.k.j2` - Override the root deployment configuration
## Usage
By default, provctl's standard KCL templates are used. To customize for syntaxis:
1. Copy the corresponding template from provctl's config/gen/templates/kcl/
2. Place it in this directory
3. Modify for syntaxis-specific needs
4. Run: `provctl gen deployment --config .provctl/gen.toml`
## Example Customization
For example, to add syntaxis-specific service metadata to schemas:
```kcl
schema Service:
# ... standard fields ...
# Syntaxis-specific
vapora_taskservs_enabled: bool = true
metrics_collection: bool = true
audit_trail: bool = true
```
## Fallback Behavior
If template files are not present here, provctl will use the default templates from:
`~/.config/provctl/gen/templates/`
This allows syntaxis to use standard templates while having the option to customize later.