chore: fix docs after fences fix
This commit is contained in:
parent
182a2f47e5
commit
d0b6b9b759
@ -137,4 +137,4 @@ All documentation is standard GitHub Flavored Markdown. You can:
|
||||
- **Looking for API docs** → See [API Reference](src/api-reference/)
|
||||
- **Want architecture details** → Read [Architecture Overview](src/architecture/architecture-overview.md)
|
||||
|
||||
For complete navigation, see [Table of Contents](src/SUMMARY.md).
|
||||
For complete navigation, see [Table of Contents](src/SUMMARY.md).
|
||||
|
||||
@ -941,4 +941,4 @@ See [LICENSE](LICENSE) file in project root.
|
||||
|
||||
**Maintained By**: Architecture Team
|
||||
**Last Updated**: 2025-10-07
|
||||
**Project Home**: [provisioning/](provisioning/)
|
||||
**Project Home**: [provisioning/](provisioning/)
|
||||
|
||||
@ -382,4 +382,4 @@ This project welcomes contributions! See **[Development Guide](development/READM
|
||||
|
||||
**Maintained By**: Provisioning Team
|
||||
**Last Review**: 2025-10-06
|
||||
**Next Review**: 2026-01-06
|
||||
**Next Review**: 2026-01-06
|
||||
|
||||
@ -168,4 +168,4 @@ The AI integration is documented in:
|
||||
|
||||
**Version**: 1.0
|
||||
**Last Updated**: 2025-01-08
|
||||
**Status**: Active
|
||||
**Status**: Active
|
||||
|
||||
@ -529,4 +529,4 @@ improve_from_feedback = true
|
||||
**Last Updated**: 2025-01-13
|
||||
**Component**: typdialog-ag
|
||||
**Architecture**: Complete
|
||||
**Implementation**: In Design Phase
|
||||
**Implementation**: In Design Phase
|
||||
|
||||
@ -435,4 +435,4 @@ Natural Language Generation AI-Assisted Forms
|
||||
**Last Updated**: 2025-01-13
|
||||
**Component**: typdialog-ai
|
||||
**Architecture**: Complete
|
||||
**Implementation**: In Design Phase
|
||||
**Implementation**: In Design Phase
|
||||
|
||||
@ -191,4 +191,4 @@ See [Configuration Guide](configuration.md) for:
|
||||
|
||||
**Last Updated**: 2025-01-13
|
||||
**Status**: ✅ Production-Ready (core system)
|
||||
**Test Coverage**: 22/22 tests passing
|
||||
**Test Coverage**: 22/22 tests passing
|
||||
|
||||
@ -61,4 +61,4 @@ Generated Configuration
|
||||
|
||||
**Status**: 🔴 Planned
|
||||
**Expected Release**: Q2 2025
|
||||
**Priority**: High (enables non-technical users to generate configs)
|
||||
**Priority**: High (enables non-technical users to generate configs)
|
||||
|
||||
@ -598,4 +598,4 @@ url = "surreal://surrealdb-cluster:8000"
|
||||
|
||||
**Last Updated**: 2025-01-13
|
||||
**Status**: ✅ Production-Ready
|
||||
**Versions Supported**: v1.0+
|
||||
**Versions Supported**: v1.0+
|
||||
|
||||
@ -494,4 +494,4 @@ monthly_budget_warning_percent = 70
|
||||
**Status**: ✅ Production-Ready
|
||||
**Average Savings**: 50-80% through caching
|
||||
**Typical Cost**: $50-500/month per organization
|
||||
**ROI**: 100:1 to 10,000:1 depending on use case
|
||||
**ROI**: 100:1 to 10,000:1 depending on use case
|
||||
|
||||
@ -591,4 +591,4 @@ RUST_LOG=provisioning::mcp=debug provisioning-mcp-server
|
||||
**Last Updated**: 2025-01-13
|
||||
**Status**: ✅ Production-Ready
|
||||
**MCP Version**: 0.6.0+
|
||||
**Supported LLMs**: Claude, GPT-4, Llama, Mistral, all MCP-compatible models
|
||||
**Supported LLMs**: Claude, GPT-4, Llama, Mistral, all MCP-compatible models
|
||||
|
||||
@ -466,4 +466,4 @@ provisioning ai generate
|
||||
**Target Release**: Q2 2025
|
||||
**Last Updated**: 2025-01-13
|
||||
**Architecture**: Complete
|
||||
**Implementation**: In Design Phase
|
||||
**Implementation**: In Design Phase
|
||||
|
||||
@ -447,4 +447,4 @@ log_context_used = true # Log context retrieved
|
||||
**Last Updated**: 2025-01-13
|
||||
**Status**: ✅ Production-Ready
|
||||
**Test Coverage**: 22/22 tests passing
|
||||
**Database**: SurrealDB 1.5.0+
|
||||
**Database**: SurrealDB 1.5.0+
|
||||
|
||||
@ -534,4 +534,4 @@ provisioning policy update ai-policies.cedar
|
||||
**Last Updated**: 2025-01-13
|
||||
**Status**: ✅ Production-Ready
|
||||
**Compliance**: PCI-DSS, HIPAA, SOX, GDPR
|
||||
**Cedar Version**: 3.0+
|
||||
**Cedar Version**: 3.0+
|
||||
|
||||
@ -499,4 +499,4 @@ log_window_seconds = 300
|
||||
**Last Updated**: 2025-01-13
|
||||
**Status**: ✅ Production-Ready
|
||||
**Success Rate**: 85-95% accuracy in root cause identification
|
||||
**Supported**: All deployment types (infrastructure, Kubernetes, database)
|
||||
**Supported**: All deployment types (infrastructure, Kubernetes, database)
|
||||
|
||||
@ -25,4 +25,4 @@ curl -X POST http://localhost:9090/workflows/servers/create
|
||||
-d '{"infra": "my-project", "servers": ["web-01"]}'
|
||||
```
|
||||
|
||||
See [REST API](rest-api.md) for complete endpoint documentation.
|
||||
See [REST API](rest-api.md) for complete endpoint documentation.
|
||||
|
||||
@ -1202,4 +1202,4 @@ Common issues and solutions.
|
||||
4. **Audit Logging**: Log all security-relevant operations
|
||||
5. **Encryption**: Encrypt sensitive data in transit and at rest
|
||||
|
||||
This extension development API provides a comprehensive framework for building robust, scalable, and maintainable extensions for provisioning.
|
||||
This extension development API provides a comprehensive framework for building robust, scalable, and maintainable extensions for provisioning.
|
||||
|
||||
@ -1589,4 +1589,4 @@ class EventDrivenWorkflowManager {
|
||||
```
|
||||
|
||||
This comprehensive integration documentation provides developers with everything needed to successfully integrate with provisioning, including
|
||||
complete client implementations, error handling strategies, performance optimizations, and common integration patterns.
|
||||
complete client implementations, error handling strategies, performance optimizations, and common integration patterns.
|
||||
|
||||
@ -108,4 +108,4 @@ Browse the complete source code:
|
||||
|
||||
---
|
||||
|
||||
For integration examples, see [Integration Examples](integration-examples.md).
|
||||
For integration examples, see [Integration Examples](integration-examples.md).
|
||||
|
||||
@ -727,4 +727,4 @@ Path resolution respects file system permissions:
|
||||
- Workspace directories may require write access for operations
|
||||
|
||||
This path resolution API provides a comprehensive and flexible system for managing the complex path requirements of multi-provider, multi-environment
|
||||
infrastructure provisioning.
|
||||
infrastructure provisioning.
|
||||
|
||||
@ -183,4 +183,4 @@ Current API version: `2.0.0`
|
||||
|
||||
---
|
||||
|
||||
For more examples, see [Integration Examples](integration-examples.md).
|
||||
For more examples, see [Integration Examples](integration-examples.md).
|
||||
|
||||
@ -1115,4 +1115,4 @@ cargo test --test api_tests
|
||||
|
||||
# Run load tests
|
||||
cargo test --test load_tests --release
|
||||
```
|
||||
```
|
||||
|
||||
@ -1094,4 +1094,4 @@ async fn main() -> Result<(), Box<dyn std::error::Error>> {
|
||||
4. **Load Testing**: Validate performance under load
|
||||
|
||||
This comprehensive SDK documentation provides developers with everything needed to integrate with provisioning using their preferred programming
|
||||
language, complete with examples, best practices, and detailed API references.
|
||||
language, complete with examples, best practices, and detailed API references.
|
||||
|
||||
@ -889,4 +889,4 @@ The server implements rate limiting to prevent abuse:
|
||||
- PII and secrets are never transmitted
|
||||
|
||||
This WebSocket API provides a robust, real-time communication channel for monitoring and managing provisioning with comprehensive security and
|
||||
performance features.
|
||||
performance features.
|
||||
|
||||
@ -115,4 +115,4 @@ Organize by architectural layers (presentation/, business/, data/).
|
||||
- Configuration System Migration (ADR-002)
|
||||
- Hybrid Architecture Decision (ADR-004)
|
||||
- Extension Framework Design (ADR-005)
|
||||
- Project Architecture Principles (PAP) Guidelines
|
||||
- Project Architecture Principles (PAP) Guidelines
|
||||
|
||||
@ -176,4 +176,4 @@ System Defaults (lowest precedence)
|
||||
- Workspace Isolation Decision (ADR-003)
|
||||
- Configuration System Migration (CLAUDE.md)
|
||||
- User Experience Guidelines (Design Principles)
|
||||
- Installation and Deployment Procedures
|
||||
- Installation and Deployment Procedures
|
||||
|
||||
@ -188,4 +188,4 @@ provisioning workspace migrate --from-version 2.0.0 --to-version 3.0.0
|
||||
- Configuration System Migration (CLAUDE.md)
|
||||
- Security Guidelines (Design Principles)
|
||||
- Extension Framework (ADR-005)
|
||||
- Multi-User Deployment Patterns
|
||||
- Multi-User Deployment Patterns
|
||||
|
||||
@ -207,4 +207,4 @@ Run Nushell and coordination layer in separate containers.
|
||||
- Configuration-Driven Architecture (ADR-002)
|
||||
- Batch Workflow System (CLAUDE.md - v3.1.0)
|
||||
- Integration Patterns Documentation
|
||||
- Performance Benchmarking Results
|
||||
- Performance Benchmarking Results
|
||||
|
||||
@ -281,4 +281,4 @@ export def uninstall [server: string] -> nothing {
|
||||
- Hybrid Architecture Integration (ADR-004)
|
||||
- Community Extension Guidelines
|
||||
- Extension Security Framework
|
||||
- Extension Development Documentation
|
||||
- Extension Development Documentation
|
||||
|
||||
@ -387,4 +387,4 @@ The new architecture enables:
|
||||
|
||||
---
|
||||
|
||||
*This ADR documents a major architectural improvement completed on 2025-09-30.*
|
||||
*This ADR documents a major architectural improvement completed on 2025-09-30.*
|
||||
|
||||
@ -263,4 +263,4 @@ See `docs/migration/KMS_SIMPLIFICATION.md` for detailed steps.
|
||||
- Age is designed by Filippo Valsorda (Google, Go security team)
|
||||
- Cosmian provides FIPS 140-2 Level 3 compliance (when using certified hardware)
|
||||
- This decision aligns with project goal of reducing cloud provider dependencies
|
||||
- Migration timeline: 6 weeks for full adoption
|
||||
- Migration timeline: 6 weeks for full adoption
|
||||
|
||||
@ -349,4 +349,4 @@ with safety.
|
||||
|
||||
**Approved By**: Architecture Team
|
||||
**Implementation Date**: 2025-10-08
|
||||
**Review Date**: 2026-01-08 (Quarterly)
|
||||
**Review Date**: 2026-01-08 (Quarterly)
|
||||
|
||||
@ -658,4 +658,4 @@ cargo test --test break_glass_integration_tests
|
||||
|
||||
**Date**: 2025-10-08
|
||||
**Version**: 1.0.0
|
||||
**Status**: Implemented and Production-Ready
|
||||
**Status**: Implemented and Production-Ready
|
||||
|
||||
@ -410,4 +410,4 @@ provisioning/templates/
|
||||
|
||||
---
|
||||
|
||||
**Last Updated**: 2025-12-03
|
||||
**Last Updated**: 2025-12-03
|
||||
|
||||
@ -476,4 +476,4 @@ typedialog form --input form.toml --output nickel
|
||||
|
||||
**Last Updated**: 2025-12-15
|
||||
**Version**: 1.0.0
|
||||
**Implementation**: Complete (Phase 1-4 finished, workspace-level in progress)
|
||||
**Implementation**: Complete (Phase 1-4 finished, workspace-level in progress)
|
||||
|
||||
@ -376,4 +376,4 @@ Plugin integrates with provisioning config system:
|
||||
**Status**: Accepted and Implemented
|
||||
**Last Updated**: 2025-12-15
|
||||
**Implementation**: Complete
|
||||
**Tests**: Passing
|
||||
**Tests**: Passing
|
||||
|
||||
@ -589,4 +589,4 @@ export PROVISIONING_INTERACTIVE=true
|
||||
**Last Updated**: 2025-01-08
|
||||
**Implementation**: Planned
|
||||
**Priority**: High (User onboarding and security)
|
||||
**Estimated Complexity**: Moderate
|
||||
**Estimated Complexity**: Moderate
|
||||
|
||||
@ -656,4 +656,4 @@ export VAULT_CACERT="/etc/provisioning/vault-ca.pem"
|
||||
**Last Updated**: 2025-01-08
|
||||
**Implementation**: Planned
|
||||
**Priority**: High (Security and compliance)
|
||||
**Estimated Complexity**: Complex
|
||||
**Estimated Complexity**: Complex
|
||||
|
||||
@ -1120,4 +1120,4 @@ With caching (50% hit rate):
|
||||
**Last Updated**: 2025-01-08
|
||||
**Implementation**: Planned (High Priority)
|
||||
**Estimated Complexity**: Very Complex
|
||||
**Dependencies**: ADR-008, ADR-011, ADR-013, ADR-014
|
||||
**Dependencies**: ADR-008, ADR-011, ADR-013, ADR-014
|
||||
|
||||
@ -156,4 +156,4 @@ CI/CD enforces: schema hash == generated code
|
||||
- Nickel Language: [https://nickel-lang.org/](https://nickel-lang.org/)
|
||||
- Nushell 0.109 Guidelines: `.claude/guidelines/nushell.md`
|
||||
- Current Accessor Implementation: `provisioning/core/nulib/lib_provisioning/config/accessor.nu`
|
||||
- Schema Source: `provisioning/schemas/config/settings/contracts.ncl`
|
||||
- Schema Source: `provisioning/schemas/config/settings/contracts.ncl`
|
||||
|
||||
@ -222,4 +222,4 @@ Allows parallel operation and gradual migration.
|
||||
|
||||
- Nushell 0.109 Guidelines: `.claude/guidelines/nushell.md`
|
||||
- Do-Complete Pattern: Error handling without try-catch
|
||||
- Plugin Framework: `provisioning/core/nulib/lib_provisioning/plugins/`
|
||||
- Plugin Framework: `provisioning/core/nulib/lib_provisioning/plugins/`
|
||||
|
||||
@ -277,4 +277,4 @@ es-ES = ["en-US"]
|
||||
- Fluent Syntax: [https://projectfluent.org/fluent/guide/](https://projectfluent.org/fluent/guide/)
|
||||
- Nushell 0.109 Guidelines: `.claude/guidelines/nushell.md`
|
||||
- Current Help Implementation: `provisioning/core/nulib/main_provisioning/help_system.nu`
|
||||
- Fluent Files: `provisioning/locales/{en-US,es-ES}/help.ftl`
|
||||
- Fluent Files: `provisioning/locales/{en-US,es-ES}/help.ftl`
|
||||
|
||||
@ -259,4 +259,4 @@ let config = (load-provisioning-config)
|
||||
|
||||
- Current Implementation: `provisioning/core/nulib/lib_provisioning/config/loader.nu`
|
||||
- Cache System: `provisioning/core/nulib/lib_provisioning/config/cache/`
|
||||
- Nushell 0.109 Guidelines: `.claude/guidelines/nushell.md`
|
||||
- Nushell 0.109 Guidelines: `.claude/guidelines/nushell.md`
|
||||
|
||||
@ -309,4 +309,4 @@ Both paths work without breaking existing code.
|
||||
|
||||
- Current Implementation: `provisioning/core/nulib/main_provisioning/commands/`
|
||||
- Nushell 0.109 Guidelines: `.claude/guidelines/nushell.md`
|
||||
- Module System: Nushell module documentation
|
||||
- Module System: Nushell module documentation
|
||||
|
||||
@ -1334,4 +1334,4 @@ Zones:
|
||||
|
||||
**Maintained By**: Architecture Team
|
||||
**Review Cycle**: Quarterly
|
||||
**Next Review**: 2026-01-06
|
||||
**Next Review**: 2026-01-06
|
||||
|
||||
@ -263,4 +263,4 @@ time ./provisioning help infrastructure
|
||||
- `loader.nu` - Full configuration loading system
|
||||
- `loader-minimal.nu` - Fast path loader
|
||||
- `loader-lazy.nu` - Smart loader decision logic
|
||||
- `config/ARCHITECTURE.md` - Configuration architecture details
|
||||
- `config/ARCHITECTURE.md` - Configuration architecture details
|
||||
|
||||
@ -382,4 +382,4 @@ server_url = "http://localhost:9998" # Cosmian KMS server
|
||||
|
||||
- [Configuration System](../infrastructure/configuration-guide.md)
|
||||
- [KMS Architecture](../security/kms-architecture.md)
|
||||
- [Workspace Switching](../infrastructure/workspace-switching-guide.md)
|
||||
- [Workspace Switching](../infrastructure/workspace-switching-guide.md)
|
||||
|
||||
@ -419,4 +419,4 @@ Success in applying these principles is measured by:
|
||||
- Performance and scalability characteristics
|
||||
- Security and isolation effectiveness
|
||||
|
||||
These principles represent the distilled wisdom from building and operating complex infrastructure automation systems at scale.
|
||||
These principles represent the distilled wisdom from building and operating complex infrastructure automation systems at scale.
|
||||
|
||||
@ -520,4 +520,4 @@ Currently we implement **Phase 1** with selective integration.
|
||||
- **Provctl**: `/Users/Akasha/Development/provctl/`
|
||||
- **Rust Guidelines**: See Rust Development
|
||||
- **Nushell Guidelines**: See Nushell Development
|
||||
- **Nickel Guidelines**: See Nickel Module System
|
||||
- **Nickel Guidelines**: See Nickel Module System
|
||||
|
||||
@ -620,4 +620,4 @@ mod integration_tests {
|
||||
```
|
||||
|
||||
These integration patterns provide the foundation for the system's sophisticated multi-component architecture, enabling reliable, scalable, and
|
||||
maintainable infrastructure automation.
|
||||
maintainable infrastructure automation.
|
||||
|
||||
@ -707,4 +707,4 @@ provisioning workspace migrate-to-oci workspace_prod
|
||||
|
||||
**Maintained By**: Architecture Team
|
||||
**Review Cycle**: Quarterly
|
||||
**Next Review**: 2026-01-06
|
||||
**Next Review**: 2026-01-06
|
||||
|
||||
@ -1022,4 +1022,4 @@ concerns while maintaining integration through a well-designed package system.
|
||||
4. **Implement package registry**
|
||||
5. **Begin repository extraction**
|
||||
|
||||
Would you like me to create a detailed **repository split implementation plan** next?
|
||||
Would you like me to create a detailed **repository split implementation plan** next?
|
||||
|
||||
@ -770,4 +770,4 @@ These examples are:
|
||||
|
||||
**Version**: 1.0.0
|
||||
**Status**: Tested & Verified
|
||||
**Last Updated**: 2025-12-15
|
||||
**Last Updated**: 2025-12-15
|
||||
|
||||
@ -1204,4 +1204,4 @@ let ts_youki = import "./taskservs/youki.ncl" in
|
||||
|
||||
**Version**: 1.0.0
|
||||
**Status**: Complete Reference Guide
|
||||
**Last Updated**: 2025-12-15
|
||||
**Last Updated**: 2025-12-15
|
||||
|
||||
@ -618,4 +618,4 @@ cargo test security_integration_tests
|
||||
|
||||
**Maintained By**: Security Team
|
||||
**Review Cycle**: Quarterly
|
||||
**Last Reviewed**: 2025-10-08
|
||||
**Last Reviewed**: 2025-10-08
|
||||
|
||||
@ -146,4 +146,4 @@ Does this clear it up? The orchestrator is the performance and reliability layer
|
||||
Cost: $0.1565 USD
|
||||
Duration: 137.69s
|
||||
Turns: 40
|
||||
Total tokens: 7466(7 in, 7459 out)
|
||||
Total tokens: 7466(7 in, 7459 out)
|
||||
|
||||
@ -800,4 +800,4 @@ While Nushell provides:
|
||||
- Configuration management (KCL integration)
|
||||
- User-facing scripting
|
||||
|
||||
**Multi-repo just splits WHERE the code lives, not HOW it works together.**
|
||||
**Multi-repo just splits WHERE the code lives, not HOW it works together.**
|
||||
|
||||
@ -407,4 +407,4 @@ provisioning server create --infra . --check
|
||||
- Module dependency resolution
|
||||
- Automatic version updates
|
||||
- Module templates and scaffolding
|
||||
- Integration with external package managers
|
||||
- Integration with external package managers
|
||||
|
||||
@ -1608,4 +1608,4 @@ enterprise deployments.
|
||||
- Rust cargo packaging conventions
|
||||
- npm/yarn package management patterns
|
||||
- Homebrew formula best practices
|
||||
- KCL package management design
|
||||
- KCL package management design
|
||||
|
||||
@ -352,4 +352,4 @@ The system solves fundamental technical challenges through architectural innovat
|
||||
- **Workflow Engine**: Custom workflow definitions and execution
|
||||
|
||||
This system architecture represents a mature, production-ready platform for Infrastructure as Code with unique architectural innovations and proven
|
||||
scalability.
|
||||
scalability.
|
||||
|
||||
@ -949,4 +949,4 @@ TypeDialog + Nickel provides:
|
||||
|
||||
**Version**: 1.0.0
|
||||
**Status**: Implementation Guide
|
||||
**Last Updated**: 2025-12-15
|
||||
**Last Updated**: 2025-12-15
|
||||
|
||||
@ -628,4 +628,4 @@ vim ~/workspaces/dev/config/provisioning.yaml
|
||||
- [Migration Guide](./MIGRATION_GUIDE.md)
|
||||
- [Workspace Guide](./WORKSPACE_GUIDE.md)
|
||||
- [Schema Files](../config/*.schema.toml)
|
||||
- [Validation Tests](../tests/config_validation_tests.nu)
|
||||
- [Validation Tests](../tests/config_validation_tests.nu)
|
||||
|
||||
@ -533,4 +533,4 @@ Scenario: 20 sequential commands
|
||||
|
||||
**For Support**: See `docs/troubleshooting-guide.md`
|
||||
**For Architecture**: See `docs/architecture/`
|
||||
**For User Guide**: See `docs/user/AUTHENTICATION_LAYER_GUIDE.md`
|
||||
**For User Guide**: See `docs/user/AUTHENTICATION_LAYER_GUIDE.md`
|
||||
|
||||
@ -1073,4 +1073,4 @@ make ci-release
|
||||
```
|
||||
|
||||
This build system provides a comprehensive, maintainable foundation for the provisioning project's development lifecycle, from local development to
|
||||
production releases.
|
||||
production releases.
|
||||
|
||||
@ -611,4 +611,4 @@ For questions or issues, refer to ADR-006 or ask the team.
|
||||
|
||||
---
|
||||
|
||||
*This guide is part of the provisioning project documentation. Last updated: 2025-09-30*
|
||||
*This guide is part of the provisioning project documentation. Last updated: 2025-09-30*
|
||||
|
||||
@ -51,4 +51,4 @@ provisioning <command> help
|
||||
|
||||
---
|
||||
|
||||
For complete command documentation, see [Service Management Guide](SERVICE_MANAGEMENT_GUIDE.md).
|
||||
For complete command documentation, see [Service Management Guide](SERVICE_MANAGEMENT_GUIDE.md).
|
||||
|
||||
@ -292,4 +292,4 @@ if $result.exit_code == 1 and ($result.stderr | str contains "password is requir
|
||||
|
||||
- **2025-01-XX**: Initial implementation with return values (v2)
|
||||
- **2025-01-XX**: Fixed mutable variable capture with `reduce` pattern
|
||||
- **2025-01-XX**: First attempt with `exit 130` (reverted, caused process termination)
|
||||
- **2025-01-XX**: First attempt with `exit 130` (reverted, caused process termination)
|
||||
|
||||
@ -981,4 +981,4 @@ interpolation_cache = true
|
||||
```
|
||||
|
||||
This configuration management system provides a robust, flexible foundation that supports development workflows while maintaining production
|
||||
reliability and security requirements.
|
||||
reliability and security requirements.
|
||||
|
||||
@ -912,4 +912,4 @@ nu workspace.nu health --detailed --fix-issues
|
||||
- Monitor disk space and set up alerts
|
||||
|
||||
This workspace management system provides a robust foundation for development while maintaining isolation and providing comprehensive tools for
|
||||
maintenance and troubleshooting.
|
||||
maintenance and troubleshooting.
|
||||
|
||||
@ -1002,4 +1002,4 @@ df -h
|
||||
```
|
||||
|
||||
This distribution process provides a robust, automated pipeline for creating, validating, and distributing provisioning across multiple platforms
|
||||
while maintaining high quality and reliability standards.
|
||||
while maintaining high quality and reliability standards.
|
||||
|
||||
@ -1757,4 +1757,4 @@ provisioning workspace create <name>
|
||||
|
||||
**Maintained By**: Documentation Team
|
||||
**Review Cycle**: Quarterly or when major features are added
|
||||
**Feedback**: Please report missing or unclear terms via issues
|
||||
**Feedback**: Please report missing or unclear terms via issues
|
||||
|
||||
@ -894,4 +894,4 @@ If you encounter issues:
|
||||
1. Check the validation reports
|
||||
2. Review the rollback procedures
|
||||
3. Consult the architecture analysis
|
||||
4. Create an issue in the tracker
|
||||
4. Create an issue in the tracker
|
||||
|
||||
@ -1227,4 +1227,4 @@ company_servers: [server.Server] = [
|
||||
]
|
||||
```
|
||||
|
||||
This comprehensive guide covers all aspects of creating infrastructure-specific extensions, from assessment and planning to implementation and deployment.
|
||||
This comprehensive guide covers all aspects of creating infrastructure-specific extensions, from assessment and planning to implementation and deployment.
|
||||
|
||||
@ -1216,4 +1216,4 @@ def debug-integration-health [] -> record {
|
||||
```
|
||||
|
||||
This integration guide provides a comprehensive framework for seamlessly integrating new development components with existing production systems while
|
||||
maintaining reliability, compatibility, and clear migration pathways.
|
||||
maintaining reliability, compatibility, and clear migration pathways.
|
||||
|
||||
@ -567,4 +567,4 @@ Use this checklist to track your migration:
|
||||
The KMS simplification reduces complexity while providing better separation between development and production use cases. Age offers a fast, offline
|
||||
solution for development, while Cosmian KMS provides enterprise-grade security for production deployments.
|
||||
|
||||
For questions or issues, please refer to the documentation or open an issue.
|
||||
For questions or issues, please refer to the documentation or open an issue.
|
||||
|
||||
@ -111,4 +111,4 @@ export PROVISIONING_DEBUG=true
|
||||
|
||||
## Related Documentation
|
||||
|
||||
- **Architecture**: [MCP Integration](../architecture/orchestrator-integration-model.md)
|
||||
- **Architecture**: [MCP Integration](../architecture/orchestrator-integration-model.md)
|
||||
|
||||
@ -408,4 +408,4 @@ nu workspace/extensions/providers/my-provider/nulib/provider.nu test
|
||||
- **Testing Framework**: Built-in testing and validation tools
|
||||
|
||||
This structure represents a significant evolution in the project's organization while maintaining complete backward compatibility and providing
|
||||
powerful new development capabilities.
|
||||
powerful new development capabilities.
|
||||
|
||||
@ -345,4 +345,4 @@ See the interface specification for complete function documentation:
|
||||
get-provider-interface-docs | table
|
||||
```
|
||||
|
||||
This returns the complete API with signatures and descriptions for all provider interface functions.
|
||||
This returns the complete API with signatures and descriptions for all provider interface functions.
|
||||
|
||||
@ -397,4 +397,4 @@ Enterprise SLA AWS or UpCloud
|
||||
- **DigitalOcean**: Developer-friendly, simplicity-focused, good value
|
||||
|
||||
For most organizations, a **multi-provider strategy** combining Hetzner (compute), AWS (managed services), and DigitalOcean (edge) provides the best
|
||||
balance of cost, capability, and resilience.
|
||||
balance of cost, capability, and resilience.
|
||||
|
||||
@ -715,4 +715,4 @@ nickel typecheck nickel/main.ncl &&
|
||||
nu tests/run_{provider}_tests.nu &&
|
||||
for f in templates/*.j2; do bash -n <(sed 's/{%.*%}//' "$f"); done &&
|
||||
echo "✅ PRODUCTION READY"
|
||||
```
|
||||
```
|
||||
|
||||
@ -678,4 +678,4 @@ echo 'export PROVISIONING=/path/to/provisioning' >> ~/.zshrc
|
||||
|
||||
**Document Version**: 1.0.0
|
||||
**Last Updated**: 2025-09-29
|
||||
**Maintained by**: JesusPerezLorenzo
|
||||
**Maintained by**: JesusPerezLorenzo
|
||||
|
||||
@ -319,4 +319,4 @@ curl -H "Authorization: Bearer $PROVIDER_TOKEN" https://api.provider.com/test
|
||||
- Check existing providers for implementation patterns
|
||||
- Review the [Provider Interface Documentation](PROVIDER_AGNOSTIC_ARCHITECTURE.md#provider-interface)
|
||||
- Test with the provider test suite: `./provisioning/tools/test-provider-agnostic.nu`
|
||||
- Run migration checks: `./provisioning/tools/migrate-to-provider-agnostic.nu status`
|
||||
- Run migration checks: `./provisioning/tools/migrate-to-provider-agnostic.nu status`
|
||||
|
||||
@ -246,4 +246,4 @@ nickel format provisioning/extensions/taskservs/{category}/my-service/schemas/
|
||||
1. Read the full [Taskserv Developer Guide](TASKSERV_DEVELOPER_GUIDE.md)
|
||||
2. Explore existing taskservs in `provisioning/extensions/taskservs/`
|
||||
3. Check out templates in `provisioning/workspace/templates/taskservs/`
|
||||
4. Join the development community for support
|
||||
4. Join the development community for support
|
||||
|
||||
@ -1003,4 +1003,4 @@ provisioning config export
|
||||
|
||||
# Check generated files
|
||||
ls -la workspace_librecloud/config/generated/
|
||||
```
|
||||
```
|
||||
|
||||
@ -1062,4 +1062,4 @@ def test-with-isolation [test_name: string, test_action: closure] {
|
||||
```
|
||||
|
||||
This development workflow provides a comprehensive framework for efficient, quality-focused development while maintaining the project's architectural
|
||||
principles and ensuring smooth collaboration across the team.
|
||||
principles and ensuring smooth collaboration across the team.
|
||||
|
||||
@ -248,4 +248,4 @@ If you plan to use cloud providers, prepare credentials:
|
||||
## Next Steps
|
||||
|
||||
Once all prerequisites are met, proceed to:
|
||||
→ **[Installation](02-installation.md)**
|
||||
→ **[Installation](02-installation.md)**
|
||||
|
||||
@ -232,4 +232,4 @@ Once installation is complete, proceed to:
|
||||
|
||||
- [Detailed Installation Guide](../user/installation-guide.md)
|
||||
- [Workspace Management](../user/workspace-setup.md)
|
||||
- [Troubleshooting Guide](../user/troubleshooting-guide.md)
|
||||
- [Troubleshooting Guide](../user/troubleshooting-guide.md)
|
||||
|
||||
@ -270,4 +270,4 @@ Now that you've completed your first deployment:
|
||||
|
||||
- [Complete Deployment Guide](../guides/from-scratch.md)
|
||||
- [Infrastructure Management](../user/infrastructure-management.md)
|
||||
- [Troubleshooting Guide](../user/troubleshooting-guide.md)
|
||||
- [Troubleshooting Guide](../user/troubleshooting-guide.md)
|
||||
|
||||
@ -339,4 +339,4 @@ Once verification is complete:
|
||||
|
||||
---
|
||||
|
||||
**Congratulations!** You've successfully deployed and verified your first Provisioning Platform infrastructure!
|
||||
**Congratulations!** You've successfully deployed and verified your first Provisioning Platform infrastructure!
|
||||
|
||||
@ -496,4 +496,4 @@ After completing platform configuration:
|
||||
|
||||
**Version**: 1.0.0
|
||||
**Last Updated**: 2026-01-05
|
||||
**Difficulty**: Beginner to Intermediate
|
||||
**Difficulty**: Beginner to Intermediate
|
||||
|
||||
@ -548,4 +548,4 @@ Now that you understand the basics:
|
||||
3. **Understand configuration**: [Configuration Guide](configuration.md)
|
||||
4. **Explore examples**: [Examples and Tutorials](examples/)
|
||||
|
||||
You're ready to start building and managing cloud infrastructure with confidence!
|
||||
You're ready to start building and managing cloud infrastructure with confidence!
|
||||
|
||||
@ -533,4 +533,4 @@ After successful installation:
|
||||
3. **Learn about configuration**: `docs/user/configuration.md`
|
||||
4. **Try example tutorials**: `docs/user/examples/`
|
||||
|
||||
Your provisioning is now ready to manage cloud infrastructure!
|
||||
Your provisioning is now ready to manage cloud infrastructure!
|
||||
|
||||
@ -619,4 +619,4 @@ This guide covers:
|
||||
- ✅ Troubleshooting common issues
|
||||
- ✅ Next steps for deployment
|
||||
|
||||
You now have a fully installed and validated provisioning system ready for workspace deployment.
|
||||
You now have a fully installed and validated provisioning system ready for workspace deployment.
|
||||
|
||||
@ -1104,4 +1104,4 @@ export CONTROL_CENTER_URL="http://localhost:3000"
|
||||
**For fastest access to this guide**: `provisioning sc`
|
||||
|
||||
**Last Updated**: 2025-10-09
|
||||
**Maintained By**: Platform Team
|
||||
**Maintained By**: Platform Team
|
||||
|
||||
@ -26,4 +26,4 @@ provisioning guide from-scratch
|
||||
|
||||
---
|
||||
|
||||
For the complete step-by-step walkthrough, start with Prerequisites.
|
||||
For the complete step-by-step walkthrough, start with Prerequisites.
|
||||
|
||||
@ -829,4 +829,4 @@ rm -rf /tmp/provisioning-ci-*/
|
||||
|
||||
| **Next Step**: Choose your profile and run `provisioning setup profile --profile <developer | production | cicd>` |
|
||||
|
||||
**Need more help?** See [Setup Guide](setup.md) or [Troubleshooting](../troubleshooting/troubleshooting.md)
|
||||
**Need more help?** See [Setup Guide](setup.md) or [Troubleshooting](../troubleshooting/troubleshooting.md)
|
||||
|
||||
@ -175,4 +175,4 @@ Important files:
|
||||
|
||||
---
|
||||
|
||||
**Ready to dive deeper?** Check out the [Full Setup Guide](SETUP_SYSTEM_GUIDE.md)
|
||||
**Ready to dive deeper?** Check out the [Full Setup Guide](SETUP_SYSTEM_GUIDE.md)
|
||||
|
||||
@ -203,4 +203,4 @@ provisioning setup system --help
|
||||
|
||||
**Status**: Production Ready ✅
|
||||
**Version**: 1.0.0
|
||||
**Last Updated**: 2025-12-09
|
||||
**Last Updated**: 2025-12-09
|
||||
|
||||
@ -660,4 +660,4 @@ provisioning service logs kms
|
||||
|
||||
**Ready?** Run: `provisioning setup profile` and choose your profile!
|
||||
|
||||
**Questions?** Check [Troubleshooting](../troubleshooting/troubleshooting.md) or [Setup Profiles Guide](setup-profiles.md)
|
||||
**Questions?** Check [Troubleshooting](../troubleshooting/troubleshooting.md) or [Setup Profiles Guide](setup-profiles.md)
|
||||
|
||||
@ -843,4 +843,4 @@ provisioning tpl validate <project> # Validate template usage
|
||||
|
||||
---
|
||||
|
||||
*This guide is part of the provisioning project documentation. Last updated: 2025-09-30*
|
||||
*This guide is part of the provisioning project documentation. Last updated: 2025-09-30*
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user