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.

Sign up for GitHub

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

Jump to bottom

Migrate infrastructure around Beats to go modules #15004

Closed
3 tasks
kvch opened this issue Dec 7, 2019 · 2 comments
Closed
3 tasks

Migrate infrastructure around Beats to go modules #15004

kvch opened this issue Dec 7, 2019 · 2 comments
Labels
Team:Integrations Label for the Integrations team

Comments

@kvch
Copy link
Contributor

kvch commented Dec 7, 2019 •
edited by faec
Loading

We need to migrate the whole repository, including building and packaging Beats, to use go modules.

The first step is to add a go.mod file in: #14902

But we have additional tasks:

  • getting rid of GOPATH in packaging
  • getting rid of GOPATH in build scripts
  • check if we need additional tagging on top, so we support semver syntactically

I propose once we switch to full go modules support, we should get rid of vendoring. I would like to support only one way to handle dependencies.
@kvch kvch mentioned this issue Dec 7, 2019
Closed
4 tasks
@vjsamuel
Copy link
Contributor

vjsamuel commented Dec 8, 2019

can't wait for this one :)

@kvch
Copy link
Contributor Author

kvch commented Jan 21, 2020

Closing as tracking remains in #15683

@kvch kvch closed this as completed Jan 21, 2020
@andresrc andresrc added the Team:Integrations Label for the Integrations team label Mar 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Team:Integrations Label for the Integrations team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@andresrc @kvch @vjsamuel @faec