Do we want to bind all of these together as one cc_library, or export them individually. I ask because looking at the related envoy change envoyproxy/envoy#1039, when you are depending in eds on api_cc, you bring unrelated proto libraries in. I see the benefit of having the single bind from envoy_cc_api to api_cc, but if bazel is meant to make dependencies explicit, I would think that exporting these individually might make more sense. Thoughts?

I've switched to avoiding this. It was a convenience to avoid having to do bind for each of the libraries in the main Envoy repo, but it doesn't matter, we have to do something either side so it's fine to keep it fine grained, as you point out it's the Bazel way.