provisioning/core/nulib/lib_provisioning/extensions/profiles.nu

224 lines
6.9 KiB
Plaintext
Raw Normal View History

# Profile-based Access Control
# Implements permission system for restricted environments like CI/CD
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 ../config/accessor.nu *
# Load profile configuration
export def load-profile [profile_name?: string]: nothing -> record {
let active_profile = if ($profile_name | is-not-empty) {
$profile_name
} 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
(get-provisioning-profile)
}
if ($active_profile | is-empty) {
return {
name: "default"
allowed: {
commands: []
providers: []
taskservs: []
}
blocked: {
commands: []
providers: []
taskservs: []
}
restricted: false
}
}
# Check user profile first
let user_profile_path = ($env.HOME | path join ".provisioning-extensions" "profiles" $"($active_profile).yaml")
let system_profile_path = ("/opt/provisioning-extensions/profiles" | path join $"($active_profile).yaml")
let project_profile_path = ($env.PWD | path join ".provisioning" "profiles" $"($active_profile).yaml")
# Load in priority order: project > user > system
let available_files = [
$project_profile_path
$user_profile_path
$system_profile_path
] | where ($it | path exists)
if ($available_files | length) > 0 {
open ($available_files | first)
} else {
# Default restricted profile
{
name: $active_profile
allowed: {
commands: ["list", "status", "show", "query", "help", "version"]
providers: ["local"]
taskservs: []
}
blocked: {
commands: ["delete", "create", "sops", "secrets"]
providers: ["aws", "upcloud"]
taskservs: []
}
restricted: true
}
}
}
# Check if command is allowed
export def is-command-allowed [command: string, subcommand?: string]: nothing -> bool {
let profile = (load-profile)
if not $profile.restricted {
return true
}
let full_command = if ($subcommand | is-not-empty) {
$"($command) ($subcommand)"
} else {
$command
}
# Check blocked first
if ($profile.blocked.commands | any {|cmd| $full_command =~ $cmd}) {
return false
}
# If allowed list is empty, allow everything not blocked
if ($profile.allowed.commands | is-empty) {
return true
}
# Check if explicitly allowed
($profile.allowed.commands | any {|cmd| $full_command =~ $cmd})
}
# Check if provider is allowed
export def is-provider-allowed [provider: string]: nothing -> bool {
let profile = (load-profile)
if not $profile.restricted {
return true
}
# Check blocked first
if ($profile.blocked.providers | any {|prov| $provider == $prov}) {
return false
}
# If allowed list is empty, allow everything not blocked
if ($profile.allowed.providers | is-empty) {
return true
}
# Check if explicitly allowed
($profile.allowed.providers | any {|prov| $provider == $prov})
}
# Check if taskserv is allowed
export def is-taskserv-allowed [taskserv: string]: nothing -> bool {
let profile = (load-profile)
if not $profile.restricted {
return true
}
# Check blocked first
if ($profile.blocked.taskservs | any {|ts| $taskserv == $ts}) {
return false
}
# If allowed list is empty, allow everything not blocked
if ($profile.allowed.taskservs | is-empty) {
return true
}
# Check if explicitly allowed
($profile.allowed.taskservs | any {|ts| $taskserv == $ts})
}
# Enforce profile restrictions on command execution
export def enforce-profile [command: string, subcommand?: string, target?: string]: nothing -> bool {
if not (is-command-allowed $command $subcommand) {
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 $"🛑 Command '($command) ($subcommand | default "")' is not allowed by profile ((get-provisioning-profile))"
return false
}
# Additional checks based on target type
if ($target | is-not-empty) {
match $command {
"server" => {
if ($subcommand | default "") in ["create", "delete"] {
let settings = (find_get_settings)
let server = ($settings.data.servers | where hostname == $target | first?)
if ($server | is-not-empty) {
if not (is-provider-allowed $server.provider) {
print $"🛑 Provider '($server.provider)' is not allowed by profile"
return false
}
}
}
}
"taskserv" => {
if not (is-taskserv-allowed $target) {
print $"🛑 TaskServ '($target)' is not allowed by profile"
return false
}
}
}
}
return true
}
# Show current profile information
export def show-profile []: nothing -> record {
let profile = (load-profile)
{
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
active_profile: (get-provisioning-profile)
extension_mode: (get-extension-mode)
profile_config: $profile
status: (if $profile.restricted { "restricted" } else { "unrestricted" })
}
}
# Create example profile files
export def create-example-profiles []: nothing -> nothing {
let user_profiles_dir = ($env.HOME | path join ".provisioning-extensions" "profiles")
mkdir $user_profiles_dir
# CI/CD profile
let cicd_profile = {
profile: "cicd"
description: "Restricted profile for CI/CD agents"
restricted: true
allowed: {
commands: ["server list", "server status", "taskserv list", "taskserv status", "query", "show", "help", "version"]
providers: ["local"]
taskservs: ["kubernetes", "containerd", "kubectl"]
}
blocked: {
commands: ["server create", "server delete", "taskserv create", "taskserv delete", "sops", "secrets"]
providers: ["aws", "upcloud"]
taskservs: ["postgres", "gitea"]
}
}
# Developer profile
let developer_profile = {
profile: "developer"
description: "Profile for developers with limited production access"
restricted: true
allowed: {
commands: ["server list", "server create", "taskserv list", "taskserv create", "query", "show"]
providers: ["local", "aws"]
taskservs: []
}
blocked: {
commands: ["server delete", "sops"]
providers: ["upcloud"]
taskservs: ["postgres"]
}
}
# Save example profiles
$cicd_profile | to yaml | save ($user_profiles_dir | path join "cicd.yaml")
$developer_profile | to yaml | save ($user_profiles_dir | path join "developer.yaml")
print $"Created example profiles in ($user_profiles_dir)"
}