Skip to content

x-pack/filebeat/input/awss3: fix priority of region name configurations#36034

Merged
efd6 merged 2 commits intoelastic:mainfrom
efd6:sqs-region-name
Jul 18, 2023
Merged

x-pack/filebeat/input/awss3: fix priority of region name configurations#36034
efd6 merged 2 commits intoelastic:mainfrom
efd6:sqs-region-name

Conversation

@efd6
Copy link
Copy Markdown
Contributor

@efd6 efd6 commented Jul 11, 2023

What does this PR do?

The code currently prioritises the region configuration, even when it is not provided, against the claims of the documentation. Make a check whether it is empty before claiming a conflict and using it.

Why is it important?

The behaviour disagrees with the documentation.

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 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 in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

@efd6 efd6 self-assigned this Jul 11, 2023
@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Jul 11, 2023
@efd6 efd6 force-pushed the sqs-region-name branch from b94b58e to ba28a90 Compare July 11, 2023 07:55
@mergify

This comment was marked as outdated.

@efd6 efd6 force-pushed the sqs-region-name branch from ba28a90 to 8500eec Compare July 11, 2023 08:53
@efd6 efd6 marked this pull request as ready for review July 11, 2023 08:53
@efd6 efd6 requested a review from a team as a code owner July 11, 2023 08:53
@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Jul 11, 2023

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2023-07-16T22:12:08.834+0000

  • Duration: 134 min 7 sec

Test stats 🧪

Test Results
Failed 0
Passed 6106
Skipped 362
Total 6468

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the 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!)

@mergify

This comment was marked as outdated.

The code currently prioritises the region_name configuration, even when
it is not provided, against the claims of the documentation. Make a
check whether it is empty before claiming a conflict and using it.
@efd6 efd6 force-pushed the sqs-region-name branch from 8500eec to 468122d Compare July 12, 2023 23:04
Copy link
Copy Markdown
Contributor

@zmoog zmoog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@efd6 efd6 merged commit 57d649d into elastic:main Jul 18, 2023
mergify bot pushed a commit that referenced this pull request Jul 18, 2023
…ns (#36034)

The code currently prioritises the region_name configuration, even when
it is not provided, against the claims of the documentation. Make a
check whether it is empty before claiming a conflict and using it.

(cherry picked from commit 57d649d)
efd6 added a commit that referenced this pull request Jul 18, 2023
…ns (#36034) (#36096)

The code currently prioritises the region_name configuration, even when
it is not provided, against the claims of the documentation. Make a
check whether it is empty before claiming a conflict and using it.

(cherry picked from commit 57d649d)

Co-authored-by: Dan Kortschak <90160302+efd6@users.noreply.github.com>
Co-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com>
Scholar-Li pushed a commit to Scholar-Li/beats that referenced this pull request Feb 5, 2024
…ns (elastic#36034)

The code currently prioritises the region_name configuration, even when
it is not provided, against the claims of the documentation. Make a
check whether it is empty before claiming a conflict and using it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

8.10-candidate backport-v8.9.0 Automated backport with mergify bug Filebeat Filebeat

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants