YAML indentation guideline

[consideRatio]

In the yaml templates, we are currently mixing a lot in between the following ways. I'd like to stop thinking about what I'd do myself - can we decide on a guideline to aim for?

parent1:
  - key1: value1
  - key2: value2

parent2:
- key1: value1
- key2: value2

[consideRatio]

It seems like the most common practice is using the parent1 kind of indentation. Going with that!

[yuvipanda]

Do you know what kubernetes/charts repo does? They might have a YAML template linter we might want to adopt.

…

On Sun, Apr 1, 2018 at 8:57 AM, Erik Sundell ***@***.***> wrote: In the yaml templates, we are currently mixing a lot in between the following ways. I'd like to stop thinking about what I'd do myself - can we decide on a guideline to aim for? parent1: - key1: value1 - key2: value2 parent2: - key1: value1 - key2: value2 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#622>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAB23qARWcEijlYLLvTqjPaEcR6ENFjJks5tkPjngaJpZM4TC4Ja> .

-- Yuvi Panda T http://yuvi.in/blog

[consideRatio]

@yuvipanda I looked at some, prometheus for example, and concluded that the tended to use the first version. I also remember some generated yaml (by chartpress i think) matched that pattern.

I'll look for linters and rules setup by kubernetes charts!

[consideRatio]

@yuvipanda upon further investigation...

• it seems like kubernetes/charts linter is declared to ignore difference in indentationstyles
• I've now seen a lot of both types of list indentations, even within the same charts
• I now favor parent2 style for readability after seeing some nested lists being very tough to read with parent1 style indentation.

parent2:
- key1: value1
- key2: value2