Converting JSON to YAML using qa, without brackets in JSON

[epodegrid]

I have a YAML file that I converted into JSON using yq ea '[.]' -o=json render.yaml > render.json. This works fine but the program I use for scanning the JSON file, checkov, does not work if the root is an array i.e. if the file begins with a square bracket. So I use the command yq ea '.' -o=json render.yaml > render.json to get the output as just objects.

I need to convert this file back to YAML. Currently I use the command yq eval-all -P '.[] | split_doc' render.json > checks.yaml.This causes the error Error: bad file 'test.json': yaml: line 14: did not find expected <document start>.

Is it possible to convert the file from YAML to JSON and back, so that the intermediary file in JSON is not an array, and the final YAML file is still a single file with multiple documents?

Additional Information
Sample YAML file used:

---
# Source: prometheus/templates/rbac.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  labels:
    app: prometheus
    group: com.stakater.platform
    provider: stakater
    version: "2.2.0-rc.0"
    chart: "prometheus-1.0.32"
    release: "release-name"
    heritage: "Helm"
  name: monitoring-k8s
  namespace: default
---
# Source: prometheus/templates/configmap.yaml
apiVersion: v1
kind: ConfigMap
# document continues

JSON file that works with checkov:

{
  "apiVersion": "v1",
  "kind": "ServiceAccount",
  "metadata": {
    "name": "release-name-nginx-ingress",
    "namespace": "default",
    "labels": {
      "app.kubernetes.io/name": "release-name-nginx-ingress",
      "helm.sh/chart": "nginx-ingress-0.13.0",
      "app.kubernetes.io/managed-by": "Helm",
      "app.kubernetes.io/instance": "release-name"
    }
  }
}
{
  "apiVersion": "v1",
  "kind": "Secret",
  "metadata": {
    "name": "release-name-nginx-ingress-default-server-tls",
    "namespace": "default",
    "labels": {
      "app.kubernetes.io/name": "release-name-nginx-ingress",
      "helm.sh/chart": "nginx-ingress-0.13.0",
      "app.kubernetes.io/managed-by": "Helm",
      "app.kubernetes.io/instance": "release-name"
    }
  }
}

JSON file that yq needs to convert it into YAML. YAML output similar to first example.

[
  {
    "apiVersion": "v1",
    "kind": "ServiceAccount",
    "metadata": {
      "name": "release-name-nginx-ingress",
      "namespace": "default",
      "labels": {
        "app.kubernetes.io/name": "release-name-nginx-ingress",
        "helm.sh/chart": "nginx-ingress-0.13.0",
        "app.kubernetes.io/managed-by": "Helm",
        "app.kubernetes.io/instance": "release-name"
      }
    }
  },
  {
    "apiVersion": "v1",
    "kind": "Secret",
    "metadata": {
      "name": "release-name-nginx-ingress-default-server-tls",
      "namespace": "default",
      "labels": {
        "app.kubernetes.io/name": "release-name-nginx-ingress",
        "helm.sh/chart": "nginx-ingress-0.13.0",
        "app.kubernetes.io/managed-by": "Helm",
        "app.kubernetes.io/instance": "release-name"
      }
    }
]

[mikefarah]

The yaml standard supports multiple documents in a single file, separated by ---; whereas the JSON standard does not. It looks like checkov works regardless, which is nice - but yq will not accept that document as input.

If you'd like to bring it back - best thing I can suggest is to output the JSON in single line format (set indent to 0), then push that through to checkov.

Then to parse it back into yq, you'll need to add yaml document separators --- between each document. This should be eas(ier) because each line is a JSON document. You could use sed or something similar to replace line endings with ---.

what you want is something like:

{"d": "doc 1"}
---
{"d": "doc 2"}

[epodegrid]

Thank you for the answer. It is quite surprising that checkov supports a JSON document that is not per standard but not a YAML document that is as per revision 1.2. I'll look more into this and how I can integrate it into my program. Thanks!

[jakub-id]

@mikefarah I have the same problem with another tool. Many converters do this and spit out multiple JSON objects per file without wrapping them in an array:

{
..
}
{
..
}

It's not valid JSON but jq will work fine with this. Any chance to have a switch in yq to accept this format?