* [xpack/ftr/common] follow conventions, expose a config file
In order to make xpack/test/common ftr config easier to work with, this updates it to follow the conventions established by most other configs of exposing all services from the services module as an object that can be easily merges into local services modules.
* common config file and FtrProviderConfig are unused and unnecessary
* turns out FtrProviderContext was used...
* [failed_tests_cli] update reports with links to github issues
* reorder test report hooks so that published Junit includes modified reports
* force failures and enable dry-run mode for debugging
* auto-switch to --dry-run when running in non-tracked branches/prs
* add --skip-junit-update flag to skip mutating the reports
* remove comma after URL to support auto-linking in Jenkins
* Revert "force failures and enable dry-run mode for debugging"
This reverts commit ac0c287a3f.
* fix method call
* extend TestResult to include relevence flag rather than wrapping
* fix createFailureIssue() tests
* make report messages more consistent, append when not dry-run
* rename module
* update snapshots to not contain valid xml
* don't send authorization header if no token defined
* merge with master modified fixtures
* [NP] Expose global config to the plugins
* globalConfig in Plugin context: expose read-only methods only
* SharedGlobalConfig rework + Moving pkg, fromRoot & path utils from legacy to NP
* Updated API docs
* Fix test references to the moved utils
* Replace zip with combineLatest
* Change tests to describe/it + remove "(deprecated)" from the test description
* Moving path files to a folder + exposing the config path in the contract
* deepFreeze the globalConfig in the pluginContext
* Fix types in tests with new path.config
* Move fromRoot and package_json utils to core/server/utils
* Rename globalConfig to legacy.globalConfig$
* path.config renamed to path.configDir (not renaming path.data because it might be a breaking change)
* Change configDir in mocker as well
* Fix test after config renamed to configDir
* Fix API docs conflicts
* Rename the path properties when exposing them
* path.configDir removed from the path config-schema
* Remove path.configDir. It is already in env.configs
* Add Migration documentation and examples
* Fix 'kibana/server' imports in the MIGRATION docs
resolves https://github.com/elastic/kibana/issues/50721
note this branch was previously merged into master and then reverted: https://github.com/elastic/kibana/pull/51489 (prior PR made shape changes this one didn't take into account)
Uses the same whitelist config value / utilities that the webhook
action already uses. Was already mentioned in the README doc
that email uses this whitelist config value :-)
Required a change to the functional tests to use a host already
whitelisted in config, made for the the webhook action tests.
Also realized some jest tests on email were bogus, so fixed those
(was passing `user` in config, which is invalid, and masking the
actual thing being tested).
* Port graphql query for snapshot to hapijs
* fix type
* Remove graphql from node details.
* Use boom for error handling.
* Remove unused imports
* Remove dead code. Merge types
* Fix tests
* Remove unused import
* Rename types
* Go all in on io-ts. Cleanup types
* Fix typecheck
* Move plugin init calls to new plugin file, update refs and bind to legacy var. Assume ref for license init
* Bind server calls to __LEGACY var and pass to plugin setup
* Expose map config externally
* Pass in NP features and licensing plugins to replace some xpack_main functionality
* Pass through legacy server config for routes dependency
* Expose map config for legacy plugins
* Remove unused legacy refs
* Update license check to conform with latest NP license practices
* Clean up
* Revert to old license check. Handle NP license checking in separate PR
* Add back the license check file
* add links to plugin manifest format
* remove obsolete comment
* address comments. add registry folder to file structure tree
* revert back not confirmed conventions
resolves https://github.com/elastic/kibana/issues/50721
Uses the same whitelist config value / utilities that the webhook
action already uses. Was already mentioned in the README doc
that email uses this whitelist config value :-)
Required a change to the functional tests to use a host already
whitelisted in config, made for the the webhook action tests.
Also realized some jest tests on email were bogus, so fixed those
(was passing `user` in config, which is invalid, and masking the
actual thing being tested).
Ensure no deprecated Node.js core API's are used in Kibana. This is
achieved by throwing an error in either development mode or in CI if one
of the deprecated API's is called, and as such, new PR's should no
longer be able to be merged if they use deprecated API's.
Some of these API's (like the `Buffer` constructor`) is a security risk.
* wip: classification job config in form
* ability to create classification job in form + validation
* ensure classification types are correct for validation
* update reducer test to include jobType validity check
* update analytics jobs help text
* update newJobCapsService to support boolean fields
Instruments Kibana with Elastic APM by adding the Node.js agent to the
source code. The agent is not turned on by default but can be enabled by
setting the environment variable `ELASTIC_APM_ACTIVE=true` or by
creating an apm config file called `config/apm.dev.js` and setting
`active: true` inside of it.
This implementation is not meant to be used by end-users of Kibana as it
lacks integration with the regular Kibana config file. For now, this is
meant as a useful internal tool for Elastic employees when developing
Kibana.
By default, it's pre-configured with a `serverUrl` pointing to an APM
Server hosted on Elastic Cloud. The data is stored in an ES cluster
accessible only by Elastic employees. These defaults can easily be
overwritten using environment variables or via the custom config file.
* create new api to fetch root transaction by trace id
* redirecting trace to transaction
* redirecting trace to transaction
* redirecting trace to transaction
* testing external link
* testing external link
* testing external link
* testing external link
* changing route name
* refactoring
* refactoring
* refactoring
* fixing merge conflicts
* adding rangeFrom and to, into the url query param
* removing convertedValue from duration formatter
* refactoring ES query and tracelink component
* pr comments
* refactoring link