YAML In, YAML Out

YAML in, YAML out

Your ops team keeps each environment's connector settings in a YAML file in the deployment repo — pipelines speak YAML, not JSON. At deploy time your extension must swallow that file into setup records, and when ops snapshots an environment it must produce the same document back from those records. You are building both directions of that bridge.

Requirements

The starter ships two tables — keep their names, field names and types exactly as given, because the grading tests read and seed the records directly:

• "Env Config Setup" — primary key "Config Code" (Code[20]); fields "Environment Name" (Text[100]), Production (Boolean), "Api Base Url" (Text[250]), "Timeout Seconds" (Integer), "Retry Limit" (Integer).
• "Env Config Feature" — primary key "Config Code" (Code[20]) + Position (Integer); fields "Feature Key" (Code[30]), Enabled (Boolean).

Implement the codeunit named "Env Config Yaml" with exactly these two public procedures:

procedure ImportConfig(ConfigCode: Code[20]; YamlText: Text)
procedure ExportConfig(ConfigCode: Code[20]): Text

Keep your object IDs in the 50100–50199 range and reference other objects by name, never by ID.

The document

environment:
  name: SANDBOX-EU
  production: false
api:
  baseUrl: https://api.example.com/v2
  timeoutSeconds: 30
  retryLimit: 5
features:
  - key: TELEMETRY
    enabled: true
  - key: AUTOSYNC
    enabled: false