[8.x](backport #40993) Don't register cfgfile flags on flag.CommandLine in func init()
#41007
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.
Proposed commit message
Requires the explicit calling of
cfgfile.InitFlags(nil)to register the flags initialized by thecfgfilemodule.This is required to allow other modules to import beats without having those flags present in the global
flag.CommandLine. When they are automatically registered they collide and cause issues with other already registered command line arguments (aka. elastic-agent).Checklist
[ ] 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(not really possible to unit test)[ ] I have added an entry in(not user facing)CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Disruptive User Impact
None
This is an automatic backport of pull request #40993 done by [Mergify](https://mergify.com).