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

[Ingest Manager] Discuss: how to integrate with Registry OpenAPI #70711

Closed
jfsiii opened this issue Jul 3, 2020 · 2 comments
Closed

[Ingest Manager] Discuss: how to integrate with Registry OpenAPI #70711

jfsiii opened this issue Jul 3, 2020 · 2 comments
Labels
Team:Fleet Team label for Observability Data Collection Fleet team technical debt Improvement of the software architecture and operational architecture

Comments

@jfsiii
Copy link
Contributor

jfsiii commented Jul 3, 2020

Ingest Manger (EPM) depends on the package registry. And the package registry publishes an OpenAPI spec https://github.com/elastic/package-registry/blob/master/openapi.yml

Ingest might want to reference the available servers, generate clients, or lots of other options

How do we deal with that dependency?

Manually:

  • run script(s) to
  • import the file

Link:

  • npm dependency?
  • GitHub API: e.g.
    curl https://api.github.com/repos/elastic/package-registry/contents/openapi.yml \
        -H "Accept: application/vnd.github.raw+yaml" \
        > path/to/openapi.yml
    
  • git submodule 🤢
@jfsiii jfsiii added technical debt Improvement of the software architecture and operational architecture Team:Fleet Team label for Observability Data Collection Fleet team labels Jul 3, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/ingest-management (Team:Ingest Management)

@ph
Copy link
Contributor

ph commented Jul 16, 2020

I think I would keep it manual for now and in the kibana repository. For a few reasons.

  • We are the only consumer of the package registry.
  • The API surface is really thin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Fleet Team label for Observability Data Collection Fleet team technical debt Improvement of the software architecture and operational architecture
Projects
None yet
Development

No branches or pull requests

4 participants