handling IPv6 within square brackets

[gsantoro]

What does this PR do?

Handle [] around IPv6 in upstream servers addresses

Why is it important?

If upstream server field has an IPv6 it will not be correctly handled.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• all pipeline tests are passing. You can run the pipeline tests with

cd filebeat
GENERATE=true TESTING_FILEBEAT_MODULES=nginx TESTING_FILEBEAT_FILESETS=ingress_controller mage -v pythonIntegTest

How to test this PR locally

Related issues

• Closes IPv6 address is not correctly parsed by filebeat with the nginx_ingress_controller module #32978

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @gsantoro? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-09-07T10:05:50.946+0000

• Duration: 68 min 1 sec

Test stats 🧪

Test	Results
Failed	0
Passed	6381
Skipped	737
Total	7118

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[andrewkroh]

Relates: elastic/integrations#3117 (comment)

[andrewkroh]

Please add test data for the use case that this fixes. Add the samples to https://github.com/elastic/beats/blob/980972ea9a58bf6bb78fb190b499fbf9c17f1cc4/filebeat/module/nginx/ingress_controller/test/test.log then regenerate the expected.json file.

[gsantoro]

Please add test data for the use case that this fixes. Add the samples to https://github.com/elastic/beats/blob/980972ea9a58bf6bb78fb190b499fbf9c17f1cc4/filebeat/module/nginx/ingress_controller/test/test.log then regenerate the expected.json file.

I was looking into adding some tests but currently I can't find how to run those ingest pipeilne tests in the nginx_ingress_controller fileset. Is there something like what we use in the integrations repo (eg. elastic-package test pipeline -v).

[tetianakravchenko]

LGTM!

[gsantoro]

@Mergifyio backport 8.3

[mergify]

backport 8.3

✅ Backports have been created

• #33008 handling IPv6 within square brackets (backport #32989) has been created for branch 8.3

[Strangerxxx]

@Mergifyio backport 7.17

[mergify]

backport 7.17

❌ Command disallowed due to command restrictions in the Mergify configuration.

• sender-permission>=write

[Strangerxxx]

@gsantoro is it possible to backport this into 7.17 branch?