Fix command which installs mage #17388
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kvch
added
needs_backport
|
Pinging @elastic/integrations-services (Team:Services) |
1 task
kvch
added a commit
to kvch/beats
that referenced
this pull request
Apr 2, 2020
This PR fixes the install command of `mage`. With the adoption of go modules adding `/...` has become necessary in order to install the pacakge. This issue prevents beats from installing `mage` if it is not present. One of the symptoms of this problem is the failure to generate new Beats if `mage` is not available. (cherry picked from commit 18eb496)
kvch
added
v7.8.0
and removed
needs_backport
kvch
added a commit
to kvch/beats
that referenced
this pull request
Apr 2, 2020
This PR fixes the install command of `mage`. With the adoption of go modules adding `/...` has become necessary in order to install the pacakge. This issue prevents beats from installing `mage` if it is not present. One of the symptoms of this problem is the failure to generate new Beats if `mage` is not available. (cherry picked from commit 18eb496)
1 task
kvch
added a commit
that referenced
this pull request
Apr 3, 2020
This PR fixes the install command of `mage`. With the adoption of go modules adding `/...` has become necessary in order to install the pacakge. This issue prevents beats from installing `mage` if it is not present. One of the symptoms of this problem is the failure to generate new Beats if `mage` is not available. (cherry picked from commit 18eb496)
kvch
added a commit
that referenced
this pull request
Apr 3, 2020
This PR fixes the install command of `mage`. With the adoption of go modules adding `/...` has become necessary in order to install the pacakge. This issue prevents beats from installing `mage` if it is not present. One of the symptoms of this problem is the failure to generate new Beats if `mage` is not available. (cherry picked from commit 18eb496)
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
This PR fixes the install command of `mage`. With the adoption of go modules adding `/...` has become necessary in order to install the pacakge. This issue prevents beats from installing `mage` if it is not present. One of the symptoms of this problem is the failure to generate new Beats if `mage` is not available. (cherry picked from commit 54cdadd)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR fixes the install command of
mage. With the adoption of go modules adding/...has become necessary in order to install the pacakge.Why is it important?
This issue prevents beats from installing
mageif it is not present. One of the symptoms of this problem is the failure to generate new Beats ifmageis not available.Checklist
- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature works- [ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.