> doesn't it base64 it and save it with all the other yaml configs It does! It's mountable in the filesystem though. In this case, the data key is the filename

> doesn't it base64 it and save it with all the other yaml configs It does! It's mountable in the filesystem though. In this case, the data key is the filename, and its un-base64'd data, the file contents. > Even that seems a bit dirty though As I mentioned in the previous comment, "Perhaps not the most elegant solution" :D It's been maintenance-free for years though, and since its introduction there were 0 rollout-related 502s.