Skip to content

[tcp] Migrate package to input type #13141

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 20, 2025

Conversation

taylor-swanson
Copy link
Contributor

@taylor-swanson taylor-swanson commented Mar 17, 2025

Proposed commit message

  • Migrated the package to input type
  • Raised minimum stack version to 8.13.0
  • Update package spec version to 3.3.2

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
    - [ ] I have verified that any added dashboard complies with Kibana's Dashboard good practices

How to test this PR locally

cd packages/tcp
elastic-package test
  • Ran manual test to verify custom set values are preserved during upgrade, and that after upgrading integration policy, integration continues to write documents to a custom dataset.

Related issues

Screenshots

Screenshot 2025-03-17 at 10 15 08 AM

- Migrated the package to input type
- Raised minimum stack version to 8.13.0
- Update package spec version to 3.3.2
@taylor-swanson taylor-swanson added enhancement New feature or request Integration:tcp Custom TCP Logs Team:Security-Deployment and Devices Deployment and Devices Security team [elastic/sec-deployment-and-devices] labels Mar 17, 2025
@taylor-swanson taylor-swanson self-assigned this Mar 17, 2025
@elasticmachine
Copy link

💚 Build Succeeded

cc @taylor-swanson

Copy link

@taylor-swanson taylor-swanson marked this pull request as ready for review March 17, 2025 15:53
@taylor-swanson taylor-swanson requested a review from a team as a code owner March 17, 2025 15:53
@elasticmachine
Copy link

Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices)

@taylor-swanson taylor-swanson merged commit bcb031e into elastic:main Mar 20, 2025
7 checks passed
@taylor-swanson taylor-swanson deleted the enhance/tcp-input-pkg branch March 20, 2025 13:15
@elastic-vault-github-plugin-prod

Package tcp - 2.0.0 containing this change is available at https://epr.elastic.co/package/tcp/2.0.0/

flexitrev pushed a commit that referenced this pull request Mar 25, 2025
- Migrated the package to input type
- Raised minimum stack version to 8.13.0
- Update package spec version to 3.3.2
flexitrev pushed a commit that referenced this pull request Mar 28, 2025
- Migrated the package to input type
- Raised minimum stack version to 8.13.0
- Update package spec version to 3.3.2
flexitrev pushed a commit that referenced this pull request Mar 28, 2025
- Migrated the package to input type
- Raised minimum stack version to 8.13.0
- Update package spec version to 3.3.2
flexitrev pushed a commit that referenced this pull request Mar 28, 2025
- Migrated the package to input type
- Raised minimum stack version to 8.13.0
- Update package spec version to 3.3.2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Integration:tcp Custom TCP Logs Team:Security-Deployment and Devices Deployment and Devices Security team [elastic/sec-deployment-and-devices]
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants