Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed source from api to papi #879

Open
adriacidre opened this issue Feb 19, 2018 · 0 comments
Open

Closed source from api to papi #879

adriacidre opened this issue Feb 19, 2018 · 0 comments
Labels

Comments

@adriacidre
Copy link
Contributor

Preamble

Idea: <to be assigned>
Title: Closed source from api to papi
Status: Draft
Created: 2018-02-19

Summary

Move open source enterprise logic present on the api to the closed source papi

Product Overview

There is a lack of consistency on how enterprise code is exposed as open source on the api-gateway. So anybody can access source code suposed to be only exposed to closed source contributors.

Product Description

Actually there are some endpoints on the api refering to enterprise modules:

        "notifications/add_env"
        "notifications/add_project"
        "notifications/create"
        "notifications/delete"
        "notifications/list"
        "notifications/rm_service"
        "notifications/update"
        "envs/sync"
        "envs/resolve"
        "envs/submission"
        "envs/review"
        "policies/create"
        "policies/get"
        "policies/delete"
        "policies/list"
        "policies/update"

So on each endpoint, you have code that potentially may belong to an enterprise ernest version. This can be somehow confusing for anybody working from the open source side. Plus it can expose code potentially closed source.

As all requests on Ernest Enterprise(EE) are passing through a lightweight proxy papi, makes sense to move this specific logic to that proxy, so any enterprise requests will be captured and served by papi, while in case papi is not present they will respond with a 404.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant