Ignore "Ingest Pipeline" when "Use Logs Stream" is set

[rdner]

Setting the ingest pipeline breaks using the logs stream. We must have this fail-safe.

Proposed commit message

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

• elastic-package build
• elastic-package stack up -v --version 9.2.0
• Go to the Filestream integration, add it to a new policy
• While adding enable the logs stream, set a dataset name and an ingest pipeline, e.g.:

• On the policy screen go to Actions->View Policy and verify that the custom dataset name and the pipeline field are not there for the filestream input:

• Disable the logs stream in the integration settings of this policy and view the policy again:

The custom values are now present.

Related issues

• Follow up to Improve documentation for the "Use the logs data stream" option. #15901

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: fadedd4

History

• 💚 Build #34087 succeeded 86994c0

cc @rdner

[elastic-vault-github-plugin-prod]

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