Configuration Files¶
Detailed reference for Genifest configuration file format and options.
Work in Progress
This documentation page is being developed. Please check back soon for complete content.
Configuration File Format¶
Genifest uses YAML configuration files named genifest.yaml.
Configuration Schema¶
Metadata Section¶
metadata:
cloudHome: "." # Security boundary for file operations
paths: # Unified directory configuration
- path: "scripts" # Directory path
scripts: true # Enable script execution access
depth: 0 # Directory depth (0-based, 0=single level)
- path: "manifests"
files: true # Enable file inclusion access
depth: 1 # Go one level deep into subdirectories
- path: "files"
files: true
depth: 0
Functions Section¶
functions:
- name: "function-name"
params:
- name: "param1"
required: true
- name: "param2"
required: false
valueFrom:
# ValueFrom expression
Changes Section¶
changes:
- tag: "optional-tag"
fileSelector: "*.yaml"
documentSelector: # Optional: target specific documents
kind: "ConfigMap" # Match by resource kind
metadata.name: "app-config" # Match by name (supports dot notation)
keySelector: ".path.to.field"
valueFrom:
# ValueFrom expression
See Also¶
- Core Concepts - Understanding the configuration system
- Value Generation - ValueFrom expressions
- Quick Start - Practical examples