-
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] Show equivalent API requests #139658
[Fleet] Show equivalent API requests #139658
Conversation
e4b66f3
to
7ed62d4
Compare
@dborodyansky I am curious to have your thoughts on the bottom bar with an extra button |
7ed62d4
to
33804e8
Compare
Thanks @nchaulet. Is there a document where I can learn more about the product value and rationale for this feature? I'd like to understand the context around UI proximity to the main action on these screens vs. somewhere more subtle if this action is experimental and less anticipated. On a minor note, we might consider "View API requests" or "Preview API requests" for the label (cc: @dedemorton). Also, spacing around the new button looks a bit tight. Happy to meet and chat about this. |
No there is no document about that, I am working on that as part of ON week and experimenting with this, I think it could be a good addition in our effort to making Fleet APIs ready for beta #123150 |
Pinging @elastic/fleet (Team:Fleet) |
|
||
import { FleetErrorType } from './types'; | ||
|
||
export class IngestManagerError extends Error { |
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.
I add to move a server side service here, I think it make sense to have errors define here no?
|
||
import type { FleetErrorType } from './types'; | ||
|
||
export class IngestManagerError extends Error { |
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.
it would be great to rename this error to FleetError, though that might touch many files
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.
I will try to come with a separate PR for that (just after that one to avoid conflict) but with typescript this should be pretty easy to rename :)
...t/public/applications/fleet/sections/agent_policy/details_page/components/settings/index.tsx
Outdated
Show resolved
Hide resolved
...ins/fleet/public/applications/fleet/sections/agent_policy/edit_package_policy_page/index.tsx
Outdated
Show resolved
Hide resolved
...public/applications/fleet/sections/agent_policy/list_page/components/create_agent_policy.tsx
Outdated
Show resolved
Hide resolved
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.
LGTM, added a few nits on wording.
…how-devtools-request
@elasticmachine merge upstream |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Module Count
Async chunks
Page load bundle
Unknown metric groupsESLint disabled in files
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: cc @nchaulet |
Hi Team, We have executed 05 testcases for this feature under our Fleet Test run at Fleet 8.5.0-BC2 Feature test plan and found that it's working fine. Build details:
Hence, marking this as QA:Validated. |
Summary
That PR add a new experimental feature to Fleet to show equivalent API request to some UI actions, this can be enabled by adding the following to your Kibana config file, the feature is enabled by default but it will be easy to revert if we do not want to ship it.
We use the shared component
ViewApiRequestFlyout
(used by stack management) to show the request, this allow to copy the requests and open them in the devtools, it's similar from what it's done in the stack managment plugin see bellowUI Changes
This is the same for create/edit agent policy and package policy