provisioning/core/nulib/taskservs/create.nu

76 lines
3.7 KiB
Plaintext
Raw Permalink Normal View History

feat: Complete config-driven architecture migration v2.0.0 Transform provisioning system from ENV-based to hierarchical config-driven architecture. This represents a complete system redesign with breaking changes requiring migration. ## Migration Summary - 65+ files migrated across entire codebase - 200+ ENV variables replaced with 476 config accessors - 29 syntax errors fixed across 17 files - 92% token efficiency maintained during migration ## Core Features Added ### Hierarchical Configuration System - 6-layer precedence: defaults → user → project → infra → env → runtime - Deep merge strategy with intelligent precedence rules - Multi-environment support (dev/test/prod) with auto-detection - Configuration templates for all environments ### Enhanced Interpolation Engine - Dynamic variables: {{paths.base}}, {{env.HOME}}, {{now.date}} - Git context: {{git.branch}}, {{git.commit}}, {{git.remote}} - SOPS integration: {{sops.decrypt()}} for secrets management - Path operations: {{path.join()}} for dynamic construction - Security: circular dependency detection, injection prevention ### Comprehensive Validation - Structure, path, type, semantic, and security validation - Code injection and path traversal detection - Detailed error reporting with actionable messages - Configuration health checks and warnings ## Architecture Changes ### Configuration Management (core/nulib/lib_provisioning/config/) - loader.nu: 1600+ line hierarchical config loader with validation - accessor.nu: 476 config accessor functions replacing ENV vars ### Provider System (providers/) - AWS, UpCloud, Local providers fully config-driven - Unified middleware system with standardized interfaces ### Task Services (core/nulib/taskservs/) - Kubernetes, storage, networking, registry services migrated - Template-driven configuration generation ### Cluster Management (core/nulib/clusters/) - Complete lifecycle management through configuration - Environment-specific cluster templates ## New Configuration Files - config.defaults.toml: System defaults (84 lines) - config.*.toml.example: Environment templates (400+ lines each) - Enhanced CLI: validate, env, multi-environment support ## Security Enhancements - Type-safe configuration access through validated functions - SOPS integration for encrypted secrets management - Input validation preventing injection attacks - Environment isolation and access controls ## Breaking Changes ⚠️ ENV variables no longer supported as primary configuration ⚠️ Function signatures require --config parameter ⚠️ CLI arguments and return types modified ⚠️ Provider authentication now config-driven ## Migration Path 1. Backup current environment variables 2. Copy config.user.toml.example → config.user.toml 3. Migrate ENV vars to TOML format 4. Validate: ./core/nulib/provisioning validate config 5. Test functionality with new configuration ## Validation Results ✅ Structure valid ✅ Paths valid ✅ Types valid ✅ Semantic rules valid ✅ File references valid System ready for production use with config-driven architecture. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-23 02:36:50 +00:00
use lib_provisioning *
use utils.nu *
use handlers.nu *
use ../lib_provisioning/utils/ssh.nu *
feat: Complete config-driven architecture migration v2.0.0 Transform provisioning system from ENV-based to hierarchical config-driven architecture. This represents a complete system redesign with breaking changes requiring migration. ## Migration Summary - 65+ files migrated across entire codebase - 200+ ENV variables replaced with 476 config accessors - 29 syntax errors fixed across 17 files - 92% token efficiency maintained during migration ## Core Features Added ### Hierarchical Configuration System - 6-layer precedence: defaults → user → project → infra → env → runtime - Deep merge strategy with intelligent precedence rules - Multi-environment support (dev/test/prod) with auto-detection - Configuration templates for all environments ### Enhanced Interpolation Engine - Dynamic variables: {{paths.base}}, {{env.HOME}}, {{now.date}} - Git context: {{git.branch}}, {{git.commit}}, {{git.remote}} - SOPS integration: {{sops.decrypt()}} for secrets management - Path operations: {{path.join()}} for dynamic construction - Security: circular dependency detection, injection prevention ### Comprehensive Validation - Structure, path, type, semantic, and security validation - Code injection and path traversal detection - Detailed error reporting with actionable messages - Configuration health checks and warnings ## Architecture Changes ### Configuration Management (core/nulib/lib_provisioning/config/) - loader.nu: 1600+ line hierarchical config loader with validation - accessor.nu: 476 config accessor functions replacing ENV vars ### Provider System (providers/) - AWS, UpCloud, Local providers fully config-driven - Unified middleware system with standardized interfaces ### Task Services (core/nulib/taskservs/) - Kubernetes, storage, networking, registry services migrated - Template-driven configuration generation ### Cluster Management (core/nulib/clusters/) - Complete lifecycle management through configuration - Environment-specific cluster templates ## New Configuration Files - config.defaults.toml: System defaults (84 lines) - config.*.toml.example: Environment templates (400+ lines each) - Enhanced CLI: validate, env, multi-environment support ## Security Enhancements - Type-safe configuration access through validated functions - SOPS integration for encrypted secrets management - Input validation preventing injection attacks - Environment isolation and access controls ## Breaking Changes ⚠️ ENV variables no longer supported as primary configuration ⚠️ Function signatures require --config parameter ⚠️ CLI arguments and return types modified ⚠️ Provider authentication now config-driven ## Migration Path 1. Backup current environment variables 2. Copy config.user.toml.example → config.user.toml 3. Migrate ENV vars to TOML format 4. Validate: ./core/nulib/provisioning validate config 5. Test functionality with new configuration ## Validation Results ✅ Structure valid ✅ Paths valid ✅ Types valid ✅ Semantic rules valid ✅ File references valid System ready for production use with config-driven architecture. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-23 02:36:50 +00:00
use ../lib_provisioning/config/accessor.nu *
# Provider middleware now available through lib_provisioning
# > TaskServs create
export def "main create" [
task_name?: string # task in settings
server?: string # Server hostname in settings
...args # Args for create command
--infra (-i): string # Infra directory
--settings (-s): string # Settings path
--iptype: string = "public" # Ip type to connect
--outfile (-o): string # Output file
--taskserv_pos (-p): int # Server position in settings
--check (-c) # Only check mode no taskservs will be created
--wait (-w) # Wait taskservs to be created
--select: string # Select with task as option
--debug (-x) # Use Debug mode
--xm # Debug with PROVISIONING_METADATA
--xc # Debuc for task and services locally PROVISIONING_DEBUG_CHECK
--xr # Debug for remote taskservs PROVISIONING_DEBUG_REMOTE
--xld # Log level with DEBUG PROVISIONING_LOG_LEVEL=debug
--metadata # Error with metadata (-xm)
--notitles # not tittles
--helpinfo (-h) # For more details use options "help" (no dashes)
--out: string # Print Output format: json, yaml, text (default)
]: nothing -> nothing {
if ($out | is-not-empty) {
feat: Complete config-driven architecture migration v2.0.0 Transform provisioning system from ENV-based to hierarchical config-driven architecture. This represents a complete system redesign with breaking changes requiring migration. ## Migration Summary - 65+ files migrated across entire codebase - 200+ ENV variables replaced with 476 config accessors - 29 syntax errors fixed across 17 files - 92% token efficiency maintained during migration ## Core Features Added ### Hierarchical Configuration System - 6-layer precedence: defaults → user → project → infra → env → runtime - Deep merge strategy with intelligent precedence rules - Multi-environment support (dev/test/prod) with auto-detection - Configuration templates for all environments ### Enhanced Interpolation Engine - Dynamic variables: {{paths.base}}, {{env.HOME}}, {{now.date}} - Git context: {{git.branch}}, {{git.commit}}, {{git.remote}} - SOPS integration: {{sops.decrypt()}} for secrets management - Path operations: {{path.join()}} for dynamic construction - Security: circular dependency detection, injection prevention ### Comprehensive Validation - Structure, path, type, semantic, and security validation - Code injection and path traversal detection - Detailed error reporting with actionable messages - Configuration health checks and warnings ## Architecture Changes ### Configuration Management (core/nulib/lib_provisioning/config/) - loader.nu: 1600+ line hierarchical config loader with validation - accessor.nu: 476 config accessor functions replacing ENV vars ### Provider System (providers/) - AWS, UpCloud, Local providers fully config-driven - Unified middleware system with standardized interfaces ### Task Services (core/nulib/taskservs/) - Kubernetes, storage, networking, registry services migrated - Template-driven configuration generation ### Cluster Management (core/nulib/clusters/) - Complete lifecycle management through configuration - Environment-specific cluster templates ## New Configuration Files - config.defaults.toml: System defaults (84 lines) - config.*.toml.example: Environment templates (400+ lines each) - Enhanced CLI: validate, env, multi-environment support ## Security Enhancements - Type-safe configuration access through validated functions - SOPS integration for encrypted secrets management - Input validation preventing injection attacks - Environment isolation and access controls ## Breaking Changes ⚠️ ENV variables no longer supported as primary configuration ⚠️ Function signatures require --config parameter ⚠️ CLI arguments and return types modified ⚠️ Provider authentication now config-driven ## Migration Path 1. Backup current environment variables 2. Copy config.user.toml.example → config.user.toml 3. Migrate ENV vars to TOML format 4. Validate: ./core/nulib/provisioning validate config 5. Test functionality with new configuration ## Validation Results ✅ Structure valid ✅ Paths valid ✅ Types valid ✅ Semantic rules valid ✅ File references valid System ready for production use with config-driven architecture. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-23 02:36:50 +00:00
set-provisioning-out $out
set-provisioning-no-terminal true
}
provisioning_init $helpinfo "taskserv create" ([($task_name | default "") ($server | default "")] | append $args)
feat: Complete config-driven architecture migration v2.0.0 Transform provisioning system from ENV-based to hierarchical config-driven architecture. This represents a complete system redesign with breaking changes requiring migration. ## Migration Summary - 65+ files migrated across entire codebase - 200+ ENV variables replaced with 476 config accessors - 29 syntax errors fixed across 17 files - 92% token efficiency maintained during migration ## Core Features Added ### Hierarchical Configuration System - 6-layer precedence: defaults → user → project → infra → env → runtime - Deep merge strategy with intelligent precedence rules - Multi-environment support (dev/test/prod) with auto-detection - Configuration templates for all environments ### Enhanced Interpolation Engine - Dynamic variables: {{paths.base}}, {{env.HOME}}, {{now.date}} - Git context: {{git.branch}}, {{git.commit}}, {{git.remote}} - SOPS integration: {{sops.decrypt()}} for secrets management - Path operations: {{path.join()}} for dynamic construction - Security: circular dependency detection, injection prevention ### Comprehensive Validation - Structure, path, type, semantic, and security validation - Code injection and path traversal detection - Detailed error reporting with actionable messages - Configuration health checks and warnings ## Architecture Changes ### Configuration Management (core/nulib/lib_provisioning/config/) - loader.nu: 1600+ line hierarchical config loader with validation - accessor.nu: 476 config accessor functions replacing ENV vars ### Provider System (providers/) - AWS, UpCloud, Local providers fully config-driven - Unified middleware system with standardized interfaces ### Task Services (core/nulib/taskservs/) - Kubernetes, storage, networking, registry services migrated - Template-driven configuration generation ### Cluster Management (core/nulib/clusters/) - Complete lifecycle management through configuration - Environment-specific cluster templates ## New Configuration Files - config.defaults.toml: System defaults (84 lines) - config.*.toml.example: Environment templates (400+ lines each) - Enhanced CLI: validate, env, multi-environment support ## Security Enhancements - Type-safe configuration access through validated functions - SOPS integration for encrypted secrets management - Input validation preventing injection attacks - Environment isolation and access controls ## Breaking Changes ⚠️ ENV variables no longer supported as primary configuration ⚠️ Function signatures require --config parameter ⚠️ CLI arguments and return types modified ⚠️ Provider authentication now config-driven ## Migration Path 1. Backup current environment variables 2. Copy config.user.toml.example → config.user.toml 3. Migrate ENV vars to TOML format 4. Validate: ./core/nulib/provisioning validate config 5. Test functionality with new configuration ## Validation Results ✅ Structure valid ✅ Paths valid ✅ Types valid ✅ Semantic rules valid ✅ File references valid System ready for production use with config-driven architecture. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-23 02:36:50 +00:00
if $debug { set-debug-enabled true }
if $metadata { set-metadata-enabled true }
let curr_settings = (find_get_settings --infra $infra --settings $settings)
feat: Complete config-driven architecture migration v2.0.0 Transform provisioning system from ENV-based to hierarchical config-driven architecture. This represents a complete system redesign with breaking changes requiring migration. ## Migration Summary - 65+ files migrated across entire codebase - 200+ ENV variables replaced with 476 config accessors - 29 syntax errors fixed across 17 files - 92% token efficiency maintained during migration ## Core Features Added ### Hierarchical Configuration System - 6-layer precedence: defaults → user → project → infra → env → runtime - Deep merge strategy with intelligent precedence rules - Multi-environment support (dev/test/prod) with auto-detection - Configuration templates for all environments ### Enhanced Interpolation Engine - Dynamic variables: {{paths.base}}, {{env.HOME}}, {{now.date}} - Git context: {{git.branch}}, {{git.commit}}, {{git.remote}} - SOPS integration: {{sops.decrypt()}} for secrets management - Path operations: {{path.join()}} for dynamic construction - Security: circular dependency detection, injection prevention ### Comprehensive Validation - Structure, path, type, semantic, and security validation - Code injection and path traversal detection - Detailed error reporting with actionable messages - Configuration health checks and warnings ## Architecture Changes ### Configuration Management (core/nulib/lib_provisioning/config/) - loader.nu: 1600+ line hierarchical config loader with validation - accessor.nu: 476 config accessor functions replacing ENV vars ### Provider System (providers/) - AWS, UpCloud, Local providers fully config-driven - Unified middleware system with standardized interfaces ### Task Services (core/nulib/taskservs/) - Kubernetes, storage, networking, registry services migrated - Template-driven configuration generation ### Cluster Management (core/nulib/clusters/) - Complete lifecycle management through configuration - Environment-specific cluster templates ## New Configuration Files - config.defaults.toml: System defaults (84 lines) - config.*.toml.example: Environment templates (400+ lines each) - Enhanced CLI: validate, env, multi-environment support ## Security Enhancements - Type-safe configuration access through validated functions - SOPS integration for encrypted secrets management - Input validation preventing injection attacks - Environment isolation and access controls ## Breaking Changes ⚠️ ENV variables no longer supported as primary configuration ⚠️ Function signatures require --config parameter ⚠️ CLI arguments and return types modified ⚠️ Provider authentication now config-driven ## Migration Path 1. Backup current environment variables 2. Copy config.user.toml.example → config.user.toml 3. Migrate ENV vars to TOML format 4. Validate: ./core/nulib/provisioning validate config 5. Test functionality with new configuration ## Validation Results ✅ Structure valid ✅ Paths valid ✅ Types valid ✅ Semantic rules valid ✅ File references valid System ready for production use with config-driven architecture. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-23 02:36:50 +00:00
let task = ((get-provisioning-args) | split row " "| get -o 0)
let options = if ($args | length) > 0 {
$args
} else {
feat: Complete config-driven architecture migration v2.0.0 Transform provisioning system from ENV-based to hierarchical config-driven architecture. This represents a complete system redesign with breaking changes requiring migration. ## Migration Summary - 65+ files migrated across entire codebase - 200+ ENV variables replaced with 476 config accessors - 29 syntax errors fixed across 17 files - 92% token efficiency maintained during migration ## Core Features Added ### Hierarchical Configuration System - 6-layer precedence: defaults → user → project → infra → env → runtime - Deep merge strategy with intelligent precedence rules - Multi-environment support (dev/test/prod) with auto-detection - Configuration templates for all environments ### Enhanced Interpolation Engine - Dynamic variables: {{paths.base}}, {{env.HOME}}, {{now.date}} - Git context: {{git.branch}}, {{git.commit}}, {{git.remote}} - SOPS integration: {{sops.decrypt()}} for secrets management - Path operations: {{path.join()}} for dynamic construction - Security: circular dependency detection, injection prevention ### Comprehensive Validation - Structure, path, type, semantic, and security validation - Code injection and path traversal detection - Detailed error reporting with actionable messages - Configuration health checks and warnings ## Architecture Changes ### Configuration Management (core/nulib/lib_provisioning/config/) - loader.nu: 1600+ line hierarchical config loader with validation - accessor.nu: 476 config accessor functions replacing ENV vars ### Provider System (providers/) - AWS, UpCloud, Local providers fully config-driven - Unified middleware system with standardized interfaces ### Task Services (core/nulib/taskservs/) - Kubernetes, storage, networking, registry services migrated - Template-driven configuration generation ### Cluster Management (core/nulib/clusters/) - Complete lifecycle management through configuration - Environment-specific cluster templates ## New Configuration Files - config.defaults.toml: System defaults (84 lines) - config.*.toml.example: Environment templates (400+ lines each) - Enhanced CLI: validate, env, multi-environment support ## Security Enhancements - Type-safe configuration access through validated functions - SOPS integration for encrypted secrets management - Input validation preventing injection attacks - Environment isolation and access controls ## Breaking Changes ⚠️ ENV variables no longer supported as primary configuration ⚠️ Function signatures require --config parameter ⚠️ CLI arguments and return types modified ⚠️ Provider authentication now config-driven ## Migration Path 1. Backup current environment variables 2. Copy config.user.toml.example → config.user.toml 3. Migrate ENV vars to TOML format 4. Validate: ./core/nulib/provisioning validate config 5. Test functionality with new configuration ## Validation Results ✅ Structure valid ✅ Paths valid ✅ Types valid ✅ Semantic rules valid ✅ File references valid System ready for production use with config-driven architecture. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-23 02:36:50 +00:00
let str_task = ((get-provisioning-args) | str replace $"($task) " "" |
str replace $"($task_name) " "" | str replace $"($server) " "")
($str_task | split row "-" | get -o 0 | default "" | str trim )
}
let other = if ($args | length) > 0 { ($args| skip 1) } else { "" }
feat: Complete config-driven architecture migration v2.0.0 Transform provisioning system from ENV-based to hierarchical config-driven architecture. This represents a complete system redesign with breaking changes requiring migration. ## Migration Summary - 65+ files migrated across entire codebase - 200+ ENV variables replaced with 476 config accessors - 29 syntax errors fixed across 17 files - 92% token efficiency maintained during migration ## Core Features Added ### Hierarchical Configuration System - 6-layer precedence: defaults → user → project → infra → env → runtime - Deep merge strategy with intelligent precedence rules - Multi-environment support (dev/test/prod) with auto-detection - Configuration templates for all environments ### Enhanced Interpolation Engine - Dynamic variables: {{paths.base}}, {{env.HOME}}, {{now.date}} - Git context: {{git.branch}}, {{git.commit}}, {{git.remote}} - SOPS integration: {{sops.decrypt()}} for secrets management - Path operations: {{path.join()}} for dynamic construction - Security: circular dependency detection, injection prevention ### Comprehensive Validation - Structure, path, type, semantic, and security validation - Code injection and path traversal detection - Detailed error reporting with actionable messages - Configuration health checks and warnings ## Architecture Changes ### Configuration Management (core/nulib/lib_provisioning/config/) - loader.nu: 1600+ line hierarchical config loader with validation - accessor.nu: 476 config accessor functions replacing ENV vars ### Provider System (providers/) - AWS, UpCloud, Local providers fully config-driven - Unified middleware system with standardized interfaces ### Task Services (core/nulib/taskservs/) - Kubernetes, storage, networking, registry services migrated - Template-driven configuration generation ### Cluster Management (core/nulib/clusters/) - Complete lifecycle management through configuration - Environment-specific cluster templates ## New Configuration Files - config.defaults.toml: System defaults (84 lines) - config.*.toml.example: Environment templates (400+ lines each) - Enhanced CLI: validate, env, multi-environment support ## Security Enhancements - Type-safe configuration access through validated functions - SOPS integration for encrypted secrets management - Input validation preventing injection attacks - Environment isolation and access controls ## Breaking Changes ⚠️ ENV variables no longer supported as primary configuration ⚠️ Function signatures require --config parameter ⚠️ CLI arguments and return types modified ⚠️ Provider authentication now config-driven ## Migration Path 1. Backup current environment variables 2. Copy config.user.toml.example → config.user.toml 3. Migrate ENV vars to TOML format 4. Validate: ./core/nulib/provisioning validate config 5. Test functionality with new configuration ## Validation Results ✅ Structure valid ✅ Paths valid ✅ Types valid ✅ Semantic rules valid ✅ File references valid System ready for production use with config-driven architecture. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-23 02:36:50 +00:00
let ops = $"((get-provisioning-args)) " | str replace $"($task_name) " "" | str trim
let run_create = {
let curr_settings = (settings_with_env $curr_settings)
feat: Complete config-driven architecture migration v2.0.0 Transform provisioning system from ENV-based to hierarchical config-driven architecture. This represents a complete system redesign with breaking changes requiring migration. ## Migration Summary - 65+ files migrated across entire codebase - 200+ ENV variables replaced with 476 config accessors - 29 syntax errors fixed across 17 files - 92% token efficiency maintained during migration ## Core Features Added ### Hierarchical Configuration System - 6-layer precedence: defaults → user → project → infra → env → runtime - Deep merge strategy with intelligent precedence rules - Multi-environment support (dev/test/prod) with auto-detection - Configuration templates for all environments ### Enhanced Interpolation Engine - Dynamic variables: {{paths.base}}, {{env.HOME}}, {{now.date}} - Git context: {{git.branch}}, {{git.commit}}, {{git.remote}} - SOPS integration: {{sops.decrypt()}} for secrets management - Path operations: {{path.join()}} for dynamic construction - Security: circular dependency detection, injection prevention ### Comprehensive Validation - Structure, path, type, semantic, and security validation - Code injection and path traversal detection - Detailed error reporting with actionable messages - Configuration health checks and warnings ## Architecture Changes ### Configuration Management (core/nulib/lib_provisioning/config/) - loader.nu: 1600+ line hierarchical config loader with validation - accessor.nu: 476 config accessor functions replacing ENV vars ### Provider System (providers/) - AWS, UpCloud, Local providers fully config-driven - Unified middleware system with standardized interfaces ### Task Services (core/nulib/taskservs/) - Kubernetes, storage, networking, registry services migrated - Template-driven configuration generation ### Cluster Management (core/nulib/clusters/) - Complete lifecycle management through configuration - Environment-specific cluster templates ## New Configuration Files - config.defaults.toml: System defaults (84 lines) - config.*.toml.example: Environment templates (400+ lines each) - Enhanced CLI: validate, env, multi-environment support ## Security Enhancements - Type-safe configuration access through validated functions - SOPS integration for encrypted secrets management - Input validation preventing injection attacks - Environment isolation and access controls ## Breaking Changes ⚠️ ENV variables no longer supported as primary configuration ⚠️ Function signatures require --config parameter ⚠️ CLI arguments and return types modified ⚠️ Provider authentication now config-driven ## Migration Path 1. Backup current environment variables 2. Copy config.user.toml.example → config.user.toml 3. Migrate ENV vars to TOML format 4. Validate: ./core/nulib/provisioning validate config 5. Test functionality with new configuration ## Validation Results ✅ Structure valid ✅ Paths valid ✅ Types valid ✅ Semantic rules valid ✅ File references valid System ready for production use with config-driven architecture. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-23 02:36:50 +00:00
set-wk-cnprov $curr_settings.wk_path
let arr_task = if $task_name == null or $task_name == "" or $task_name == "-" { [] } else { $task_name | split row "/" }
let match_task = if ($arr_task | length ) == 0 { "" } else { ($arr_task | get -o 0) }
let match_task_profile = if ($arr_task | length ) < 2 { "" } else { ($arr_task | get -o 1) }
let match_server = if $server == null or $server == "" { "" } else { $server}
on_taskservs $curr_settings $match_task $match_task_profile $match_server $iptype $check
}
match $task {
"" if $task_name == "h" => {
feat: Complete config-driven architecture migration v2.0.0 Transform provisioning system from ENV-based to hierarchical config-driven architecture. This represents a complete system redesign with breaking changes requiring migration. ## Migration Summary - 65+ files migrated across entire codebase - 200+ ENV variables replaced with 476 config accessors - 29 syntax errors fixed across 17 files - 92% token efficiency maintained during migration ## Core Features Added ### Hierarchical Configuration System - 6-layer precedence: defaults → user → project → infra → env → runtime - Deep merge strategy with intelligent precedence rules - Multi-environment support (dev/test/prod) with auto-detection - Configuration templates for all environments ### Enhanced Interpolation Engine - Dynamic variables: {{paths.base}}, {{env.HOME}}, {{now.date}} - Git context: {{git.branch}}, {{git.commit}}, {{git.remote}} - SOPS integration: {{sops.decrypt()}} for secrets management - Path operations: {{path.join()}} for dynamic construction - Security: circular dependency detection, injection prevention ### Comprehensive Validation - Structure, path, type, semantic, and security validation - Code injection and path traversal detection - Detailed error reporting with actionable messages - Configuration health checks and warnings ## Architecture Changes ### Configuration Management (core/nulib/lib_provisioning/config/) - loader.nu: 1600+ line hierarchical config loader with validation - accessor.nu: 476 config accessor functions replacing ENV vars ### Provider System (providers/) - AWS, UpCloud, Local providers fully config-driven - Unified middleware system with standardized interfaces ### Task Services (core/nulib/taskservs/) - Kubernetes, storage, networking, registry services migrated - Template-driven configuration generation ### Cluster Management (core/nulib/clusters/) - Complete lifecycle management through configuration - Environment-specific cluster templates ## New Configuration Files - config.defaults.toml: System defaults (84 lines) - config.*.toml.example: Environment templates (400+ lines each) - Enhanced CLI: validate, env, multi-environment support ## Security Enhancements - Type-safe configuration access through validated functions - SOPS integration for encrypted secrets management - Input validation preventing injection attacks - Environment isolation and access controls ## Breaking Changes ⚠️ ENV variables no longer supported as primary configuration ⚠️ Function signatures require --config parameter ⚠️ CLI arguments and return types modified ⚠️ Provider authentication now config-driven ## Migration Path 1. Backup current environment variables 2. Copy config.user.toml.example → config.user.toml 3. Migrate ENV vars to TOML format 4. Validate: ./core/nulib/provisioning validate config 5. Test functionality with new configuration ## Validation Results ✅ Structure valid ✅ Paths valid ✅ Types valid ✅ Semantic rules valid ✅ File references valid System ready for production use with config-driven architecture. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-23 02:36:50 +00:00
^$"((get-provisioning-name))" -mod taskserv update help --notitles
},
"" if $task_name == "help" => {
feat: Complete config-driven architecture migration v2.0.0 Transform provisioning system from ENV-based to hierarchical config-driven architecture. This represents a complete system redesign with breaking changes requiring migration. ## Migration Summary - 65+ files migrated across entire codebase - 200+ ENV variables replaced with 476 config accessors - 29 syntax errors fixed across 17 files - 92% token efficiency maintained during migration ## Core Features Added ### Hierarchical Configuration System - 6-layer precedence: defaults → user → project → infra → env → runtime - Deep merge strategy with intelligent precedence rules - Multi-environment support (dev/test/prod) with auto-detection - Configuration templates for all environments ### Enhanced Interpolation Engine - Dynamic variables: {{paths.base}}, {{env.HOME}}, {{now.date}} - Git context: {{git.branch}}, {{git.commit}}, {{git.remote}} - SOPS integration: {{sops.decrypt()}} for secrets management - Path operations: {{path.join()}} for dynamic construction - Security: circular dependency detection, injection prevention ### Comprehensive Validation - Structure, path, type, semantic, and security validation - Code injection and path traversal detection - Detailed error reporting with actionable messages - Configuration health checks and warnings ## Architecture Changes ### Configuration Management (core/nulib/lib_provisioning/config/) - loader.nu: 1600+ line hierarchical config loader with validation - accessor.nu: 476 config accessor functions replacing ENV vars ### Provider System (providers/) - AWS, UpCloud, Local providers fully config-driven - Unified middleware system with standardized interfaces ### Task Services (core/nulib/taskservs/) - Kubernetes, storage, networking, registry services migrated - Template-driven configuration generation ### Cluster Management (core/nulib/clusters/) - Complete lifecycle management through configuration - Environment-specific cluster templates ## New Configuration Files - config.defaults.toml: System defaults (84 lines) - config.*.toml.example: Environment templates (400+ lines each) - Enhanced CLI: validate, env, multi-environment support ## Security Enhancements - Type-safe configuration access through validated functions - SOPS integration for encrypted secrets management - Input validation preventing injection attacks - Environment isolation and access controls ## Breaking Changes ⚠️ ENV variables no longer supported as primary configuration ⚠️ Function signatures require --config parameter ⚠️ CLI arguments and return types modified ⚠️ Provider authentication now config-driven ## Migration Path 1. Backup current environment variables 2. Copy config.user.toml.example → config.user.toml 3. Migrate ENV vars to TOML format 4. Validate: ./core/nulib/provisioning validate config 5. Test functionality with new configuration ## Validation Results ✅ Structure valid ✅ Paths valid ✅ Types valid ✅ Semantic rules valid ✅ File references valid System ready for production use with config-driven architecture. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-23 02:36:50 +00:00
^$"((get-provisioning-name))" -mod taskserv update --help
_print (provisioning_options "update")
},
"c" | "create" | "" => {
feat: Complete config-driven architecture migration v2.0.0 Transform provisioning system from ENV-based to hierarchical config-driven architecture. This represents a complete system redesign with breaking changes requiring migration. ## Migration Summary - 65+ files migrated across entire codebase - 200+ ENV variables replaced with 476 config accessors - 29 syntax errors fixed across 17 files - 92% token efficiency maintained during migration ## Core Features Added ### Hierarchical Configuration System - 6-layer precedence: defaults → user → project → infra → env → runtime - Deep merge strategy with intelligent precedence rules - Multi-environment support (dev/test/prod) with auto-detection - Configuration templates for all environments ### Enhanced Interpolation Engine - Dynamic variables: {{paths.base}}, {{env.HOME}}, {{now.date}} - Git context: {{git.branch}}, {{git.commit}}, {{git.remote}} - SOPS integration: {{sops.decrypt()}} for secrets management - Path operations: {{path.join()}} for dynamic construction - Security: circular dependency detection, injection prevention ### Comprehensive Validation - Structure, path, type, semantic, and security validation - Code injection and path traversal detection - Detailed error reporting with actionable messages - Configuration health checks and warnings ## Architecture Changes ### Configuration Management (core/nulib/lib_provisioning/config/) - loader.nu: 1600+ line hierarchical config loader with validation - accessor.nu: 476 config accessor functions replacing ENV vars ### Provider System (providers/) - AWS, UpCloud, Local providers fully config-driven - Unified middleware system with standardized interfaces ### Task Services (core/nulib/taskservs/) - Kubernetes, storage, networking, registry services migrated - Template-driven configuration generation ### Cluster Management (core/nulib/clusters/) - Complete lifecycle management through configuration - Environment-specific cluster templates ## New Configuration Files - config.defaults.toml: System defaults (84 lines) - config.*.toml.example: Environment templates (400+ lines each) - Enhanced CLI: validate, env, multi-environment support ## Security Enhancements - Type-safe configuration access through validated functions - SOPS integration for encrypted secrets management - Input validation preventing injection attacks - Environment isolation and access controls ## Breaking Changes ⚠️ ENV variables no longer supported as primary configuration ⚠️ Function signatures require --config parameter ⚠️ CLI arguments and return types modified ⚠️ Provider authentication now config-driven ## Migration Path 1. Backup current environment variables 2. Copy config.user.toml.example → config.user.toml 3. Migrate ENV vars to TOML format 4. Validate: ./core/nulib/provisioning validate config 5. Test functionality with new configuration ## Validation Results ✅ Structure valid ✅ Paths valid ✅ Types valid ✅ Semantic rules valid ✅ File references valid System ready for production use with config-driven architecture. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-23 02:36:50 +00:00
let result = desktop_run_notify $"((get-provisioning-name)) taskservs create" "-> " $run_create --timeout 11sec
},
_ => {
if $task_name != "" {_print $"🛑 invalid_option ($task_name)" }
feat: Complete config-driven architecture migration v2.0.0 Transform provisioning system from ENV-based to hierarchical config-driven architecture. This represents a complete system redesign with breaking changes requiring migration. ## Migration Summary - 65+ files migrated across entire codebase - 200+ ENV variables replaced with 476 config accessors - 29 syntax errors fixed across 17 files - 92% token efficiency maintained during migration ## Core Features Added ### Hierarchical Configuration System - 6-layer precedence: defaults → user → project → infra → env → runtime - Deep merge strategy with intelligent precedence rules - Multi-environment support (dev/test/prod) with auto-detection - Configuration templates for all environments ### Enhanced Interpolation Engine - Dynamic variables: {{paths.base}}, {{env.HOME}}, {{now.date}} - Git context: {{git.branch}}, {{git.commit}}, {{git.remote}} - SOPS integration: {{sops.decrypt()}} for secrets management - Path operations: {{path.join()}} for dynamic construction - Security: circular dependency detection, injection prevention ### Comprehensive Validation - Structure, path, type, semantic, and security validation - Code injection and path traversal detection - Detailed error reporting with actionable messages - Configuration health checks and warnings ## Architecture Changes ### Configuration Management (core/nulib/lib_provisioning/config/) - loader.nu: 1600+ line hierarchical config loader with validation - accessor.nu: 476 config accessor functions replacing ENV vars ### Provider System (providers/) - AWS, UpCloud, Local providers fully config-driven - Unified middleware system with standardized interfaces ### Task Services (core/nulib/taskservs/) - Kubernetes, storage, networking, registry services migrated - Template-driven configuration generation ### Cluster Management (core/nulib/clusters/) - Complete lifecycle management through configuration - Environment-specific cluster templates ## New Configuration Files - config.defaults.toml: System defaults (84 lines) - config.*.toml.example: Environment templates (400+ lines each) - Enhanced CLI: validate, env, multi-environment support ## Security Enhancements - Type-safe configuration access through validated functions - SOPS integration for encrypted secrets management - Input validation preventing injection attacks - Environment isolation and access controls ## Breaking Changes ⚠️ ENV variables no longer supported as primary configuration ⚠️ Function signatures require --config parameter ⚠️ CLI arguments and return types modified ⚠️ Provider authentication now config-driven ## Migration Path 1. Backup current environment variables 2. Copy config.user.toml.example → config.user.toml 3. Migrate ENV vars to TOML format 4. Validate: ./core/nulib/provisioning validate config 5. Test functionality with new configuration ## Validation Results ✅ Structure valid ✅ Paths valid ✅ Types valid ✅ Semantic rules valid ✅ File references valid System ready for production use with config-driven architecture. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-23 02:36:50 +00:00
_print $"\nUse (_ansi blue_bold)((get-provisioning-name)) -h(_ansi reset) for help on commands and options"
}
}
# "" | "create"
#if not $env.PROVISIONING_DEBUG { end_run "" }
}