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] Lift up registry/{stream,extract} functions #83239

Merged
merged 4 commits into from
Nov 12, 2020

Conversation

jfsiii
Copy link
Contributor

@jfsiii jfsiii commented Nov 12, 2020

Summary

  • Move stream utility functions from server/services/epm/registry/streams.ts to server/services/epm/streams.ts
    • They're only used in registry at the moment but aren't specific to registry
  • Move archive extraction functions from server/services/epm/registry/extract.ts to server/services/epm/archive.ts
    • The Registry isn't the only service/code which needs to extract packages. Continue consolidating archive-related code under archive vs registry

@jfsiii jfsiii requested a review from a team November 12, 2020 01:23
@botelastic botelastic bot added the Team:Fleet Team label for Observability Data Collection Fleet team label Nov 12, 2020
@elasticmachine
Copy link
Contributor

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

@jfsiii jfsiii self-assigned this Nov 12, 2020
@jfsiii jfsiii added release_note:skip Skip the PR/issue when compiling release notes v7.11.0 v8.0.0 labels Nov 12, 2020
@jfsiii jfsiii requested review from skh and neptunian November 12, 2020 10:52
@skh
Copy link
Contributor

skh commented Nov 12, 2020

Are you sure about putting streams.ts directly in server/? I'm a bit worried about cluttering that level, so I'd rather have a server/utils directory and put it there, or keep it in server/services/epm/ until we know we need it plugin-wide.

@jfsiii jfsiii force-pushed the move-streams-functions-out-of-registry branch from 75a1e75 to 823b9b6 Compare November 12, 2020 14:14
Copy link
Contributor

@skh skh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the change!

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@jfsiii jfsiii merged commit 208e86e into elastic:master Nov 12, 2020
jfsiii pushed a commit to jfsiii/kibana that referenced this pull request Nov 12, 2020
…#83239)

## Summary

  * Move stream utility functions from `server/services/epm/registry/streams.ts` to `server/services/epm/streams.ts`
    * They're only used in registry at the moment but aren't specific to registry 
  * Move archive extraction functions from `server/services/epm/registry/extract.ts` to `server/services/epm/archive.ts`
    * The Registry isn't the only service/code which needs to extract packages. Continue consolidating archive-related code under archive vs registry
gmmorris added a commit to gmmorris/kibana that referenced this pull request Nov 12, 2020
* master:
  [Ingest Manager] Lift up registry/{stream,extract} functions (elastic#83239)
  [Reporting] Move "common" types and constants to allow cross-plugin integration (elastic#83198)
  [Lens] Add suffix formatter (elastic#82852)
  [App Search] Version documentation links (elastic#83245)
  Use saved object references for dashboard drilldowns (elastic#82602)
  Btsymbala/registered av (elastic#81910)
  [APM] Errors table for service overview (elastic#83065)
jfsiii pushed a commit that referenced this pull request Nov 12, 2020
…#83305)

## Summary

  * Move stream utility functions from `server/services/epm/registry/streams.ts` to `server/services/epm/streams.ts`
    * They're only used in registry at the moment but aren't specific to registry 
  * Move archive extraction functions from `server/services/epm/registry/extract.ts` to `server/services/epm/archive.ts`
    * The Registry isn't the only service/code which needs to extract packages. Continue consolidating archive-related code under archive vs registry
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release_note:skip Skip the PR/issue when compiling release notes Team:Fleet Team label for Observability Data Collection Fleet team v7.11.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants