Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.backend.python beat.backend.python
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beat
  • beat.backend.pythonbeat.backend.python
  • Issues
  • #8

Closed
Open
Created Jul 21, 2015 by Laurent EL SHAFEY@laurent.el-shafey

Split beat.core and beat.backend.python

Following a discussion with @andre.anjos , few beat.core functionalities need to be in beat.backend.python.

To achieve this, we need to:

  1. Move all the relevant code from beat.core to beat.backend.python
  2. Make beat.core depends on beat.backend.python
  3. Make all packages use features from beat.backend.python (when they were moved from beat.core to beat.backend.python)
Assignee
Assign to
Time tracking