Skip to content

Conversation

@jsoriano
Copy link
Member

@jsoriano jsoriano commented Oct 29, 2025

Fix #3036.

Default dataset in integration packages is formed as <package name>.<data stream name>, both in elastic-package and Fleet.

In the case of input packages, elastic-package was forming it as something like <package name>.<policy template name>, but Fleet uses only the policy template name.

Do the same as Fleet for input packages.

Default dataset in integration packages is formed as <package name>.<data stream name>,
both in elastic-package and Fleet.

In the case of input packages, elastic-package was forming it as something like
<package name>.<policy template name>, but Fleet uses only the policy template name.

Do the same as Fleet for input packages.
@jsoriano jsoriano requested a review from a team October 29, 2025 18:52
@jsoriano jsoriano self-assigned this Oct 29, 2025
@jsoriano
Copy link
Member Author

test integrations

@elastic-vault-github-plugin-prod

Created or updated PR in integrations repository to test this version. Check elastic/integrations#15808

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

cc @jsoriano

@jsoriano
Copy link
Member Author

Failures in cel and websockets in elastic/integrations#15808 are probably related, I will take a look.

@jsoriano
Copy link
Member Author

Failures in cel and websockets in elastic/integrations#15808 are probably related, I will take a look.

These packages set a default value for the data_stream.dataset variable. This will need to be taken into account.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

System tests should use the policy template name as default dataset for input packages

2 participants