[Fleet] Fix ssl config overridden from advanced yaml in full agent policy#219902
Merged
juliaElastic merged 2 commits intoelastic:mainfrom May 6, 2025
Merged
Conversation
botelastic
bot
added
the
Team:Fleet
Contributor
|
Pinging @elastic/fleet (Team:Fleet) |
Collaborator
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) ✅ license/snyk check is complete. No issues have been found. (View Details) |
Contributor
💚 Build Succeeded
Metrics [docs]
History
|
Contributor
|
Starting backport for target branches: 8.17, 8.18, 8.19, 9.0 |
Contributor
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
kibanamachine
added
the
backport missing
Contributor
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
juliaElastic
added a commit
to juliaElastic/kibana
that referenced
this pull request
May 7, 2025
…licy (elastic#219902) Issue reported by users, when ssl config is added in advanced yaml in Logstash output, it is not there in full agent policy. To verify: - create Logstash output with Advanced YAML config: ``` ssl: verification_mode: "none" ``` - use output in agent policy, go to View policy - check that the full policy yaml includes `verification_mode` <img width="447" alt="image" src="https://github.com/user-attachments/assets/4aeaa51d-64b3-4555-a8f6-44b83106c8ae" /> - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
juliaElastic
added a commit
to juliaElastic/kibana
that referenced
this pull request
May 7, 2025
…licy (elastic#219902) Issue reported by users, when ssl config is added in advanced yaml in Logstash output, it is not there in full agent policy. To verify: - create Logstash output with Advanced YAML config: ``` ssl: verification_mode: "none" ``` - use output in agent policy, go to View policy - check that the full policy yaml includes `verification_mode` <img width="447" alt="image" src="https://github.com/user-attachments/assets/4aeaa51d-64b3-4555-a8f6-44b83106c8ae" /> - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
This was referenced May 7, 2025
juliaElastic
added a commit
to juliaElastic/kibana
that referenced
this pull request
May 7, 2025
…licy (elastic#219902) Issue reported by users, when ssl config is added in advanced yaml in Logstash output, it is not there in full agent policy. To verify: - create Logstash output with Advanced YAML config: ``` ssl: verification_mode: "none" ``` - use output in agent policy, go to View policy - check that the full policy yaml includes `verification_mode` <img width="447" alt="image" src="https://github.com/user-attachments/assets/4aeaa51d-64b3-4555-a8f6-44b83106c8ae" /> - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
juliaElastic
added a commit
to juliaElastic/kibana
that referenced
this pull request
May 7, 2025
…licy (elastic#219902) Issue reported by users, when ssl config is added in advanced yaml in Logstash output, it is not there in full agent policy. To verify: - create Logstash output with Advanced YAML config: ``` ssl: verification_mode: "none" ``` - use output in agent policy, go to View policy - check that the full policy yaml includes `verification_mode` <img width="447" alt="image" src="https://github.com/user-attachments/assets/4aeaa51d-64b3-4555-a8f6-44b83106c8ae" /> - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
juliaElastic
added a commit
that referenced
this pull request
May 8, 2025
kibanamachine
removed
the
backport missing
akowalska622
pushed a commit
to akowalska622/kibana
that referenced
this pull request
May 29, 2025
…licy (elastic#219902) ## Summary Issue reported by users, when ssl config is added in advanced yaml in Logstash output, it is not there in full agent policy. To verify: - create Logstash output with Advanced YAML config: ``` ssl: verification_mode: "none" ``` - use output in agent policy, go to View policy - check that the full policy yaml includes `verification_mode` <img width="447" alt="image" src="https://github.com/user-attachments/assets/4aeaa51d-64b3-4555-a8f6-44b83106c8ae" /> ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
qn895
pushed a commit
to qn895/kibana
that referenced
this pull request
Jun 3, 2025
…licy (elastic#219902) ## Summary Issue reported by users, when ssl config is added in advanced yaml in Logstash output, it is not there in full agent policy. To verify: - create Logstash output with Advanced YAML config: ``` ssl: verification_mode: "none" ``` - use output in agent policy, go to View policy - check that the full policy yaml includes `verification_mode` <img width="447" alt="image" src="https://github.com/user-attachments/assets/4aeaa51d-64b3-4555-a8f6-44b83106c8ae" /> ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
10 tasks
juliaElastic
added a commit
that referenced
this pull request
Aug 4, 2025
## Summary Fix bug introduced with #219902. SSL config was not added to full agent policy from elasticsearch output types To verify: - Add output preconfig to `kibana.yml` ``` xpack.fleet.outputs: - hosts: - https://localhost:9200 id: eck-fleet-agent-output-elasticsearch name: eck-elasticsearch ssl: certificate_authorities: - /test/ca.crt type: elasticsearch ``` - Create agent policy and use preconfigured output - Check full agent policy (View policy on UI) that ssl config is under outputs <img width="624" height="666" alt="image" src="https://github.com/user-attachments/assets/a8342646-d2db-4791-a6f9-4b7a602f240f" /> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Aug 4, 2025
## Summary Fix bug introduced with elastic#219902. SSL config was not added to full agent policy from elasticsearch output types To verify: - Add output preconfig to `kibana.yml` ``` xpack.fleet.outputs: - hosts: - https://localhost:9200 id: eck-fleet-agent-output-elasticsearch name: eck-elasticsearch ssl: certificate_authorities: - /test/ca.crt type: elasticsearch ``` - Create agent policy and use preconfigured output - Check full agent policy (View policy on UI) that ssl config is under outputs <img width="624" height="666" alt="image" src="https://github.com/user-attachments/assets/a8342646-d2db-4791-a6f9-4b7a602f240f" /> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... (cherry picked from commit 4ef6c5d)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Aug 4, 2025
## Summary Fix bug introduced with elastic#219902. SSL config was not added to full agent policy from elasticsearch output types To verify: - Add output preconfig to `kibana.yml` ``` xpack.fleet.outputs: - hosts: - https://localhost:9200 id: eck-fleet-agent-output-elasticsearch name: eck-elasticsearch ssl: certificate_authorities: - /test/ca.crt type: elasticsearch ``` - Create agent policy and use preconfigured output - Check full agent policy (View policy on UI) that ssl config is under outputs <img width="624" height="666" alt="image" src="https://github.com/user-attachments/assets/a8342646-d2db-4791-a6f9-4b7a602f240f" /> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... (cherry picked from commit 4ef6c5d)
szaffarano
pushed a commit
to szaffarano/kibana
that referenced
this pull request
Aug 5, 2025
## Summary Fix bug introduced with elastic#219902. SSL config was not added to full agent policy from elasticsearch output types To verify: - Add output preconfig to `kibana.yml` ``` xpack.fleet.outputs: - hosts: - https://localhost:9200 id: eck-fleet-agent-output-elasticsearch name: eck-elasticsearch ssl: certificate_authorities: - /test/ca.crt type: elasticsearch ``` - Create agent policy and use preconfigured output - Check full agent policy (View policy on UI) that ssl config is under outputs <img width="624" height="666" alt="image" src="https://github.com/user-attachments/assets/a8342646-d2db-4791-a6f9-4b7a602f240f" /> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...
delanni
pushed a commit
to delanni/kibana
that referenced
this pull request
Aug 5, 2025
## Summary Fix bug introduced with elastic#219902. SSL config was not added to full agent policy from elasticsearch output types To verify: - Add output preconfig to `kibana.yml` ``` xpack.fleet.outputs: - hosts: - https://localhost:9200 id: eck-fleet-agent-output-elasticsearch name: eck-elasticsearch ssl: certificate_authorities: - /test/ca.crt type: elasticsearch ``` - Create agent policy and use preconfigured output - Check full agent policy (View policy on UI) that ssl config is under outputs <img width="624" height="666" alt="image" src="https://github.com/user-attachments/assets/a8342646-d2db-4791-a6f9-4b7a602f240f" /> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...
juliaElastic
added a commit
to juliaElastic/kibana
that referenced
this pull request
Aug 6, 2025
## Summary Fix bug introduced with elastic#219902. SSL config was not added to full agent policy from elasticsearch output types To verify: - Add output preconfig to `kibana.yml` ``` xpack.fleet.outputs: - hosts: - https://localhost:9200 id: eck-fleet-agent-output-elasticsearch name: eck-elasticsearch ssl: certificate_authorities: - /test/ca.crt type: elasticsearch ``` - Create agent policy and use preconfigured output - Check full agent policy (View policy on UI) that ssl config is under outputs <img width="624" height="666" alt="image" src="https://github.com/user-attachments/assets/a8342646-d2db-4791-a6f9-4b7a602f240f" /> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...
juliaElastic
added a commit
to juliaElastic/kibana
that referenced
this pull request
Aug 6, 2025
## Summary Fix bug introduced with elastic#219902. SSL config was not added to full agent policy from elasticsearch output types To verify: - Add output preconfig to `kibana.yml` ``` xpack.fleet.outputs: - hosts: - https://localhost:9200 id: eck-fleet-agent-output-elasticsearch name: eck-elasticsearch ssl: certificate_authorities: - /test/ca.crt type: elasticsearch ``` - Create agent policy and use preconfigured output - Check full agent policy (View policy on UI) that ssl config is under outputs <img width="624" height="666" alt="image" src="https://github.com/user-attachments/assets/a8342646-d2db-4791-a6f9-4b7a602f240f" /> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...
juliaElastic
added a commit
to juliaElastic/kibana
that referenced
this pull request
Aug 6, 2025
## Summary Fix bug introduced with elastic#219902. SSL config was not added to full agent policy from elasticsearch output types To verify: - Add output preconfig to `kibana.yml` ``` xpack.fleet.outputs: - hosts: - https://localhost:9200 id: eck-fleet-agent-output-elasticsearch name: eck-elasticsearch ssl: certificate_authorities: - /test/ca.crt type: elasticsearch ``` - Create agent policy and use preconfigured output - Check full agent policy (View policy on UI) that ssl config is under outputs <img width="624" height="666" alt="image" src="https://github.com/user-attachments/assets/a8342646-d2db-4791-a6f9-4b7a602f240f" /> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...
juliaElastic
added a commit
that referenced
this pull request
Aug 6, 2025
juliaElastic
added a commit
that referenced
this pull request
Aug 6, 2025
juliaElastic
added a commit
that referenced
this pull request
Aug 6, 2025
NicholasPeretti
pushed a commit
to NicholasPeretti/kibana
that referenced
this pull request
Aug 18, 2025
## Summary Fix bug introduced with elastic#219902. SSL config was not added to full agent policy from elasticsearch output types To verify: - Add output preconfig to `kibana.yml` ``` xpack.fleet.outputs: - hosts: - https://localhost:9200 id: eck-fleet-agent-output-elasticsearch name: eck-elasticsearch ssl: certificate_authorities: - /test/ca.crt type: elasticsearch ``` - Create agent policy and use preconfigured output - Check full agent policy (View policy on UI) that ssl config is under outputs <img width="624" height="666" alt="image" src="https://github.com/user-attachments/assets/a8342646-d2db-4791-a6f9-4b7a602f240f" /> ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Issue reported by users, when ssl config is added in advanced yaml in Logstash output, it is not there in full agent policy.
To verify:
verification_modeChecklist