[Fleet] Output Secrets Backend #169221
Merged
[Fleet] Output Secrets Backend #169221
Conversation
This file contains 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
botelastic
bot
added
the
Team:Fleet
|
Pinging @elastic/fleet (Team:Fleet) |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
juliaElastic
approved these changes
Oct 18, 2023
juliaElastic
added
the
release_note:feature
jloleysens
approved these changes
Oct 19, 2023
2 tasks
|
@elasticmachine merge upstream |
hop-dev
force-pushed
the
output-secrets
branch
from
659eecb
to
32ea487
Compare
|
@elasticmachine merge upstream |
jrodewig
approved these changes
Oct 24, 2023
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Page load bundle
History
To update your PR or re-run it, just comment with: cc @hop-dev |
kibanamachine
added
v8.12.0
backport:skip
hop-dev
added a commit
that referenced
this pull request
Oct 25, 2023
## Summary Continuation of #169221. Part of #157458 _Note: The experimental feature flag `outputSecretsStorage` must be enabled to see these changes._ Introduces the UI components to create and edit output secrets, currently there are only 3 output secrets: - Kafka output password - Kafka output SSL key - Logstash output SSL key Some key behaviours of the new UI: - on creating an output, the user can opt to revert to using plain text values if they want - once an output has been created with a secret, when editing the output, the secret values can only be replaced, never viewed - If an output uses plain values, there currently isn't a way to convert to using secrets. **Create** <img width="1639" alt="Screenshot 2023-10-24 at 14 48 49" src="https://github.com/elastic/kibana/assets/3315046/4f1d6715-70bb-4a91-a619-78cbc37106d7"> **Edit** https://github.com/elastic/kibana/assets/3315046/d8d44911-81d3-4a06-a0ff-ece981a36496 --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Had to recreate this after pinging the whole of Kibana accidentally on the last one :D
Part of #157458
Adds the ability to sepcify secrets in outputs. Currently the following secrets are supported:
The behaviour is as follows:
Secrets are only enabled if a fleet server of 8.10.0 or greater is connected.
Integration tests added for all scenarios.