9. 1. 183; Problem The indentation of sub-keys with 4 spaces in generated YAML files is inconsistent with Drupal's coding standards. This special case was a constant confusion for novices working on config conversion patches. Goal Consistently indent with 2 spaces. Heres a sample etcnetplan config for Ubuntu 18.04. HUGE LIFE PRO TIP against all expectations of decency, netplan refuses to function if you dont indent everything exactly the way it likes it and returns incomprehensible wharrgarbl errors like mapping values are not allowed in this context, line 17, column 15 if you, for example, have a single extra space.

YAML does not include any mandatory spaces. Further, there is no need to be consistent. The valid YAML indentation is shown below . You should remember the following rules while working with indentation in YAMLFlow blocks must be intended with at least some spaces with surrounding current block level. Flow content of YAML spans multiple lines.

Jun 04, 2017 &183; . Inconsistent indentation.

The config is done in yaml and yaml is indentation sensitive. You need to match indentation for each level and amount of whitespace used for each level depth must be consistent. You must also be consistent on tabs vs spaces. I am having an inconsistent indentation problem in a netplan configuration. I would like, if possible, someone to. If what you have posted is exactly as it appears in your file, then you do have inconsistent indentation . Indentations in YAML are very specific. Would you please copy your text without edits directly from your file and post it between code tags many thanks for the fast reply. I am not sure how to copypaste from VI, so i attached a printscreen.