kcl import will generate invalid file

[ShiroDN]

kcl import will generate invalid file

[Peefy]

Thank you for your feedback. The right generated KCL should be

apiVersion = "v1"
kind = "ConfigMap"
metadata = {
    name = "release-name-filebeat-daemonset-config"
    labels = {
        app = "release-name-filebeat"
        chart = "filebeat-8.5.1"
        heritage = "Helm"
        release = "release-name"
    }
}
data = {
    "filebeat.yml" = r"""filebeat.inputs:
- type: container
  paths:
    - /var/log/containers/*.log
  processors:
    - add_kubernetes_metadata:
      host: ${NODE_NAME}
      matchers:
      - logs_path:
        logs_path: "/var/log/containers/"
    
output.elasticsearch:
  host: '${NODE_NAME}'
  hosts: '["https://${ELASTICSEARCH_HOSTS:elasticsearch-master:9200}"]'
  username: '${ELASTICSEARCH_USERNAME}'
  password: '${ELASTICSEARCH_PASSWORD}'
  protocol: https
  ssl.certificate_authorities: ["/usr/share/filebeat/certs/ca.crt"]
"""
}

@jakezhu9 Do you have time to fix it? Expected to release this fix in v0.7.1. Additionally, I suggest adding more testing cases for typical scenarios, such as Kubernetes manifest list, Github Action YAML, etc.