kibana
kibana copied to clipboard
[Fleet] Fix output encryption when AAD fields or encrypted field change
Description
Resolve https://github.com/elastic/kibana/issues/176702 That PR fix output saved object encryption error when editing field that are included in AAD or an encrypted field.
For this that PR make sure that we include all required AAD field when updating an encrypted field, and that we update encrypted field when updating a required AAD field.
Tests
I added some unit tests to cover that
You can manually test this by creating a preconfigured output with allow_edit
xpack.fleet.outputs:
- name: 'Test output'
is_default: true
is_default_monitoring: true
type: 'logstash'
id: 'output-123'
hosts: ['elasticsearch:9200']
allow_edit: ['ssl', 'secrets', 'test']
ssl:
certificate: 'replace2'
key: 'replacet'
then update allow_edit
to remove the test
value, you can also check that you can update ssl certificate in the UI
:robot: GitHub comments
Expand to view the GitHub comments
Just comment with:
-
/oblt-deploy
: Deploy a Kibana instance using the Observability test environments. -
/oblt-deploy-serverless
: Deploy a serverless Kibana instance using the Observability test environments. -
run
elasticsearch-ci/docs
: Re-trigger the docs validation. (use unformatted text in the comment!)
/ci
Pinging @elastic/fleet (Team:Fleet)
@elasticmachine merge upstream
@elasticmachine merge upstream
@elasticmachine merge upstream
@elasticmachine merge upstream
@elasticmachine merge upstream
@elasticmachine merge upstream
:green_heart: Build Succeeded
- Buildkite Build
- Commit: 0a6d0eb2212de926d6dadd49df56c16248e61d43
Metrics [docs]
✅ unchanged
History
- :broken_heart: Build #193902 failed b5275d51f3f0d55ca34001e9ade607c973e72e5e
- :broken_heart: Build #193860 failed 224bf887c702dc4b4176f667af85377c754c4dfc
- :broken_heart: Build #193801 failed b57e3550abde0919b0aaf55fa17aae90556d74f7
- :broken_heart: Build #193719 failed 72595dbb67b3afed809a450854afa923b69fadab
- :broken_heart: Build #193711 failed 5bd1b8d65fbb2a7c61abbebafdd518577d7b7f98
To update your PR or re-run it, just comment with:
@elasticmachine merge upstream
cc @nchaulet
💚 All backports created successfully
Status | Branch | Result |
---|---|---|
✅ | 8.13 |
Note: Successful backport PRs will be merged automatically after passing CI.
Questions ?
Please refer to the Backport tool documentation