why is services a list/slice and not map

[surajssd]

why are services as list

services:
- name: database
  ...
- name: web
  ...
- name: cache
  ...

and not map, like this?

services:
  database:
  ...
  web:
  ...
  cache:
  ...

[surajssd]

I think I found answers to my own question:

• We will lose out on the order when we create map
• Mapping something that is map in the opencompose and putting it into something that is list in k8s, will make it hard for us to test since the order will always be different. To get more context about this see the issue in kompose update generated artifacts for k8s and openshift so that env variables are loaded in a particular order kubernetes/kompose#596
• We can add things like oc explain, when keys are definite.
• We are convertor tool and someone will git checkin the output config, if the order is changing everytime then there will be a lot of diff which is not good in terms of UX.
• More context and explaination in this PR add secrets proposal #105 (comment)

Hence closing.