-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fleet] Fix error rendering policy editor #141705
[Fleet] Fix error rendering policy editor #141705
Conversation
Pinging @elastic/fleet (Team:Fleet) |
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks okay to me but I am curious to get a little more context on what was failing and what the skipArchive
flag is doing here?
The This flag apparently interacts poorly with input packages for reasons I don't quite understand yet. See Mark's comment here: #141671 (comment) I'm hoping to land this PR then continue working on #137751 this week to track down any issues with upgrades from non-input -> input packages that are related to this |
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: cc @kpollich |
Co-authored-by: Kibana Machine <[email protected]> (cherry picked from commit 5d48265)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
Co-authored-by: Kibana Machine <[email protected]> (cherry picked from commit 5d48265) Co-authored-by: Kyle Pollich <[email protected]>
Summary
Fixes an error when rendering the "edit policy" screen.
cc @dominiqueclarke @hop-dev
Think this fix actually breaks our upgrade support for non-input packages -> input packages, but it will unblock everything else so I'd like to ship it.