You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Relates to #104986 (remote ES outputs)
Relates to #166360 (preconfigured output secrets)
Summary
As support for remote ES outputs and preconfigured output secrets were developed in parallel, there remain a couple of issues to iron out.
Preconfiguration validation
The preconfiguration validation is missing the new remote Elasticsearch type for outputs. For this reason, Kibana currently crashes when a remote ES output is defined in kibana.yml:
FATAL Error: [config validation of [xpack.fleet].outputs.2]: types that failed validation:
- [config validation of [xpack.fleet].outputs.2.0.type]: expected value to equal [elasticsearch]
- [config validation of [xpack.fleet].outputs.2.1.type]: expected value to equal [logstash]
- [config validation of [xpack.fleet].outputs.2.2.type]: expected value to equal [kafka]
jillguyonnet
changed the title
[Fleet] Preconfiguration config should allow remote Elasticsearch outputs
[Fleet] Fixes for preconfigured remote Elasticsearch outputs
Dec 5, 2023
## Summary
Closes#172546
### Testing
1. Add the following to your Kibana config file and start Kibana:
```yml
xpack.fleet.outputs:
- id: my-remote-es-output-with-a-secret
name: preconfigured remote elasticsearch output with a secret
type: remote_elasticsearch
hosts: ['http://localhost:9997']
secrets:
service_token: secretRemoteESServiceToken
```
2. Head to Fleet UI and check that the output was correctly created.
3. Go to the Dev Tools Console and query Fleet secrets: `GET
.fleet-secrets/_search`. Check that the service token secret was
created.
4. Edit the output configuration, e.g. the value of the service token,
and wait for Kibana to restart.
5. Check that the value(s) have been correctly updated.
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Relates to #104986 (remote ES outputs)
Relates to #166360 (preconfigured output secrets)
Summary
As support for remote ES outputs and preconfigured output secrets were developed in parallel, there remain a couple of issues to iron out.
Preconfiguration validation
The preconfiguration validation is missing the new remote Elasticsearch type for outputs. For this reason, Kibana currently crashes when a remote ES output is defined in kibana.yml:
Secret values hashing
The logic in secret hashing and comparison needs to be extended to remote ES output type.
Acceptance criteria
.fleet-secrets
system index..fleet-secrets
system index.The text was updated successfully, but these errors were encountered: