Skip to content

Conversation

@kilfoyle
Copy link
Contributor

@kilfoyle kilfoyle commented Nov 21, 2024

Adds a known issue to the 8.16 and 8.15 release notes for the AWS S3 input.

Closes: elastic/ingest-docs#1491
Rel: #41735 (same change targeting 8.16)
Rel: #41733 (same change targeting 8.15)


Screenshot 2024-11-21 at 9 49 59 AM

@kilfoyle kilfoyle added docs Team:Docs Label for the Observability docs team labels Nov 21, 2024
@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 Nov 21, 2024
@mergify
Copy link
Contributor

mergify bot commented Nov 21, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @kilfoyle? 🙏.
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-8./d is the label to automatically backport to the 8./d branch. /d is the digit

@mergify
Copy link
Contributor

mergify bot commented Nov 21, 2024

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

@mergify mergify bot added the backport-8.x Automated backport to the 8.x branch with mergify label Nov 21, 2024
@kilfoyle kilfoyle added the backport-8.17 Automated backport with mergify label Nov 21, 2024
Copy link
Contributor

@kaiyan-sheng kaiyan-sheng left a comment

Choose a reason for hiding this comment

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

Should we remove the 8.17 backport label?

@kilfoyle kilfoyle merged commit bb9968a into elastic:main Nov 21, 2024
7 checks passed
@pierrehilbert
Copy link
Contributor

Should we remove the 8.17 backport label?

No we should keep it as we need to have this changelog updated on all branches

mergify bot pushed a commit that referenced this pull request Nov 21, 2024
* Add known issue for AWS S3 input (target main)

* Add known issue for AWS S3 input (target main)

(cherry picked from commit bb9968a)

# Conflicts:
#	CHANGELOG.asciidoc
mergify bot pushed a commit that referenced this pull request Nov 21, 2024
* Add known issue for AWS S3 input (target main)

* Add known issue for AWS S3 input (target main)

(cherry picked from commit bb9968a)

# Conflicts:
#	CHANGELOG.asciidoc
kilfoyle added a commit that referenced this pull request Nov 21, 2024
…#41736)

* Add known issue for AWS S3 input (target main) (#41734)

* Add known issue for AWS S3 input (target main)

* Add known issue for AWS S3 input (target main)

(cherry picked from commit bb9968a)

# Conflicts:
#	CHANGELOG.asciidoc

* Update CHANGELOG.asciidoc

---------

Co-authored-by: David Kilfoyle <[email protected]>
kilfoyle added a commit that referenced this pull request Nov 21, 2024
#41737)

* Add known issue for AWS S3 input (target main) (#41734)

* Add known issue for AWS S3 input (target main)

* Add known issue for AWS S3 input (target main)

(cherry picked from commit bb9968a)

# Conflicts:
#	CHANGELOG.asciidoc

* Update CHANGELOG.asciidoc

---------

Co-authored-by: David Kilfoyle <[email protected]>
@khushijain21 khushijain21 mentioned this pull request Jun 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-8.x Automated backport to the 8.x branch with mergify backport-8.17 Automated backport with mergify docs Team:Docs Label for the Observability docs team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add known issue for Beats S3 input polling mode bug

3 participants