GitLab API proxy

gitlab api permissions scope are all or nothing you can only grant access to the entirety of the api surface this may prove problematic for the most security conscious customers, most notably because the api includes https //docs gitlab com/ee/api/repository files html proxying the gitlab api we have created the https //github com/echoeshq/gitlab proxy to give our users the ability to use echoes together with gitlab while benefiting from stronger security guarantees it can proxy api calls to a self hosted gitlab instance or to the cloud hosted gitlab com with the following added benefits the proxy limits the set of exposed endpoints to the strict subset required by echoes the proxy uses its own authentication token so that you don't have to trust us to securely hold your gitlab token the proxy is preconfigured to allow connections from echoes hq exit ips a note about gitlab webhooks while the proxy limits how echoes can consume the gitlab api, it is worth noting that echoes still installs https //docs gitlab com/ee/user/project/integrations/webhooks html and subscribes to webhook events therefore, while inbound api requests are proxied, outbound webhook events are emitted directly from your gitlab instance toward our infrastructure you can review the content of these events in the https //docs gitlab com/ee/user/project/integrations/webhook events html