edge-connect-client/sdk/examples/comprehensive/EdgeConnectConfig.yaml

# Is there a swagger file for the new EdgeConnect API?
#

kind: edgeconnect-deployment
metadata:
  name: "edge-app-demo"
spec:
  # dockerApp:
  #   appName: "edge-app-demo"
  #   appVersion: "1.0.0"
  #   manifestFile: "./docker-compose.yaml"
  #   image: "https://registry-1.docker.io/library/nginx:latest"
  k8sApp:
    appName: "edge-app-demo" # appinstance name is $appName-$appVersion-instance
    appVersion: "1.0.1"
    manifestFile: "./k8s-deployment.yaml" # store hash of the manifest file in annotation field. Annotations is a comma separated map of arbitrary key value pairs,
  infraTemplate:
    - organization: "edp2"
      region: "EU"
      cloudletOrg: "TelekomOP"
      cloudletName: "Munich"
      flavorName: "EU.small"
  network:
    outboundConnections:
      - protocol: "tcp"
        portRangeMin: 80
        portRangeMax: 80
        remoteCIDR: "0.0.0.0/0"
      - protocol: "tcp"
        portRangeMin: 443
        portRangeMax: 443
        remoteCIDR: "0.0.0.0/0"
feat(apply): Implement EdgeConnect configuration parsing foundation - Add comprehensive YAML configuration types for EdgeConnectConfig - Implement robust parser with validation and path resolution - Support both k8sApp and dockerApp configurations - Add comprehensive test coverage with real example parsing - Create validation for infrastructure uniqueness and port ranges - Generate instance names following pattern: appName-appVersion-instance 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> 2025-09-29 16:18:35 +02:00			`# Is there a swagger file for the new EdgeConnect API?`
			`#`

			`kind: edgeconnect-deployment`
			`metadata:`
			`name: "edge-app-demo"`
			`spec:`
			`# dockerApp:`
			`# appName: "edge-app-demo"`
			`# appVersion: "1.0.0"`
			`# manifestFile: "./docker-compose.yaml"`
			`# image: "https://registry-1.docker.io/library/nginx:latest"`
			`k8sApp:`
			`appName: "edge-app-demo" # appinstance name is $appName-$appVersion-instance`
feat(apply): Implement CLI command with comprehensive deployment workflow - Add edge-connect apply command with -f/--file and --dry-run flags - Integrate config parser, deployment planner, and resource manager - Provide comprehensive error handling and progress reporting - Support deployment confirmation prompts and result summaries - Move internal packages to public SDK packages for CLI access - Update all tests to pass with new package structure - Complete Phase 4 CLI Command Implementation 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> 2025-09-29 17:24:59 +02:00			`appVersion: "1.0.1"`
feat(apply): Implement EdgeConnect configuration parsing foundation - Add comprehensive YAML configuration types for EdgeConnectConfig - Implement robust parser with validation and path resolution - Support both k8sApp and dockerApp configurations - Add comprehensive test coverage with real example parsing - Create validation for infrastructure uniqueness and port ranges - Generate instance names following pattern: appName-appVersion-instance 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> 2025-09-29 16:18:35 +02:00			`manifestFile: "./k8s-deployment.yaml" # store hash of the manifest file in annotation field. Annotations is a comma separated map of arbitrary key value pairs,`
			`infraTemplate:`
			`- organization: "edp2"`
			`region: "EU"`
			`cloudletOrg: "TelekomOP"`
			`cloudletName: "Munich"`
			`flavorName: "EU.small"`
			`network:`
			`outboundConnections:`
			`- protocol: "tcp"`
			`portRangeMin: 80`
			`portRangeMax: 80`
			`remoteCIDR: "0.0.0.0/0"`
			`- protocol: "tcp"`
			`portRangeMin: 443`
			`portRangeMax: 443`
			`remoteCIDR: "0.0.0.0/0"`