As part of #328, we attempted to compile a config.yaml in a resource bundle with the final iOS Envoy.framework.

While we were able to customize our Bazel rule to copy over the resource(s) to Envoy.framework/Resources, we found that at runtime we were unable to load the configuration file from any ObjC/Swift sources within the framework.

Some sleuthing by @goaway indicated that this is because Bazel currently drops these resources here, and thus they aren't actually available when we go to access them from within the framework.

As a workaround, we compiled in the contents of the config file we needed as a static string in C++, but it may be worth revisiting this in the future if we need to compile in additional resources.