trouble. Because there have been YAML files that I've had, or Python files, where there have been spaces. But those spaces weren't actually spaces. Those spaces were special spaces inserted into the thing by another text editor that is not open source, that runs on a Macintosh system that's not mine. And it screwed up the whole thing, because it wasn't a valid space. It was some other space, I forget the name of the space that it was. It was like one of those invisible spaces. All spaces are invisible, but it's a space that was like, I don't know, I want to say non-breaking space, but it wasn't that. It was something different. And it was exclusively because of that character that the YAML script, or the YAML file, the playbook, was not executing. Because there was this non-space character, and everything that you tried to parse it through, or send it through, would fail with an illegal indentation. That was the error. It wasn't detecting necessarily, I think, that there was an illegal (50/54)
You are viewing a single comment's thread from: