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

Design Proxies collection and schema #1378

Closed
8 tasks
bajiat opened this issue Aug 12, 2016 · 2 comments
Closed
8 tasks

Design Proxies collection and schema #1378

bajiat opened this issue Aug 12, 2016 · 2 comments
Assignees
Milestone

Comments

@bajiat
Copy link
Contributor

bajiat commented Aug 12, 2016

Create a collection that will store configuration details like base URL for API proxies, for example API Umbrella. This is distinct the from the Proxy Backends collections which contains settings for a specific API backend (e.g. rate limiting).

Definition of done

  • Proxies component exists
  • Proxies component follows folder structure of other components
  • Proxies collection exists
  • Proxies schema exists
    • Schema contains field contains fields to distinguish proxies (name)
    • Schema contains Api Umbrella configuration fields
    • Schema contains Type field with one allowed value (Api Umbrella for the time being)
    • Schema has conditional validation when type field is Api Umbrella
@frenchbread
Copy link
Contributor

@brylie Could you post the initial Proxies schema?

@bajiat
Copy link
Contributor Author

bajiat commented Aug 16, 2016

@frenchbread

Proxies

  • _id
  • name
  • description ?
  • type (allowed values: 'api-umbrella', 'kong', 'tyk')
  • settings
    • url
    • apiKey
    • authToken
      • custom validation: required if type === 'api-umbrella'
    • elastic
      • custom validation: required if type === 'api-umbrella'

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

No branches or pull requests

3 participants