-
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
[Uptime] add monitor edit and add pages #118947
[Uptime] add monitor edit and add pages #118947
Conversation
@elasticmachine merge upstream |
Pinging @elastic/uptime (Team:uptime) |
@@ -6,8 +6,10 @@ | |||
*/ | |||
|
|||
import React from 'react'; | |||
|
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.
This change triggered with linting. I'm assuming this has already been discovered by the team, and if I merge upstream before merging the PR, it'll most likely have already been resolved.
Pinging @elastic/fleet (Team:Fleet) |
…ub.com/dominiqueclarke/kibana into feature/ui-monitor-management-add-edit
…tor-management-add-edit
…tor-management-add-edit
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.
Code LGTM and browsed routes
WFG !!
} | ||
|
||
interface IPolicyConfigContextProvider { | ||
children: React.ReactNode; | ||
defaultMonitorType?: DataStream; | ||
defaultIsTLSEnabled?: boolean; | ||
defaultIsZipUrlTLSEnabled?: boolean; | ||
defaultName?: string; | ||
defaultLocations?: string[]; |
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 think this might end up becoming {id: string, label: string}[]
eventually.
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.
Thanks for the heads up.
[ConfigKeys.SOURCE_ZIP_URL]: null, | ||
[ConfigKeys.SOURCE_ZIP_USERNAME]: null, | ||
[ConfigKeys.SOURCE_ZIP_PASSWORD]: null, | ||
[ConfigKeys.SOURCE_ZIP_FOLDER]: null, | ||
[ConfigKeys.SOURCE_ZIP_PROXY_URL]: null, | ||
[ConfigKeys.SOURCE_INLINE]: null, |
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.
shouldn't all of this goes in nested way now? but i think if we want to keep parity with fleet we may have to continue using existing key format.
instead 'source.inline.zip' i mean source: {...rest}
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.
Yes, you are right that it's best to continue to do this to keep parity with fleet. The actual UI fields are mapped to the flattened keys. Keeping it this way allows us to have to do the least amount of work short term.
@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.
Fleet linting 🚀
💚 Build Succeeded
Metrics [docs]Module Count
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
The following labels were identified as gaps in your version labels and will be added automatically:
If any of these should not be on your pull request, please manually remove them. |
* add monitor edit and add pages * remove unused imports * remove unexpected console log * remove unused values Co-authored-by: Kibana Machine <[email protected]>
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
* add monitor edit and add pages * remove unused imports * remove unexpected console log * remove unused values Co-authored-by: Kibana Machine <[email protected]> Co-authored-by: Dominique Clarke <[email protected]>
* add monitor edit and add pages * remove unused imports * remove unexpected console log * remove unused values Co-authored-by: Kibana Machine <[email protected]>
Summary
Resolves elastic/uptime#409
Adds basic add and edit monitor pages, including:
Testing
This PR is an incremental step. It ensures that the existing UI components can be pulled in with enough flexibility to support both the Elastic Synthetics Integration and UI Monitor Management. It does not yet encapsulate the action of saving or editing a monitor. For that reason, a code LGTM will suffice for this incremental step, as no actions are currently implemented.