Controlling which smart proxies receive a content view

I’m interested in limiting the amount of content replicated to smart proxies as we have some niche distros with lots of packages that aren’t heavily used outside of one or two datacenters.

I’m pretty sure the only way to control which smart proxies receive a content view is by lifecycle environment association to the proxy. Is that assumption correct?

If that is the case, then I guess the appropriate thing to do is to fork my lifecycle paths into distro specifc paths/environments.

Is there a better way? This seems sub-optimal.

There is not other than by lifecycle environment today. @Justin_Sherrill can shed more light on roadmap around adding more granularity to what you can sync.