## Proposal There are three dependency proxy controllers: 1. `Groups::DependencyProxiesController` 2. `Groups::DependencyProxyForContainersController` 3. `Groups::DependencyProxyAuthController` The first is the controller that handles the Dependency Proxy UI, whereas the last two are endpoints that implement the Docker v2 API and allow external clients to communicate with the dependency proxy via API requests. Because these are two different functions, we should namespace them differently. We should place the last two controllers in their own namespace: 1. `Groups::DependencyProxy::ContainersController` 1. `Groups::DependencyProxy::AuthController` We should consider splitting `DependencyProxy::GroupAccess` in two so we can continue to use the existing concern for the UI controller, but have a different concern: `DependencyProxyClient::GroupAccess` for the client based controllers. This will help prevent any confusion with updates to permissions moving forward. This split could wait until it is needed.