Skip to content
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

Migrate /api/settings to KP #77554

Merged
merged 3 commits into from
Sep 16, 2020
Merged

Conversation

joshdover
Copy link
Contributor

Summary

Closes #76416

This migrates the /api/settings endpoint from the legacy xpack_main plugin to the xpack_legacy plugin. This plugin can be deleted once Beats is no longer using this (in 8.0).

Much of this PR is similar to #76054

Checklist

@joshdover joshdover added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v8.0.0 release_note:skip Skip the PR/issue when compiling release notes v7.10.0 Feature:Legacy Removal Issues related to removing legacy Kibana labels Sep 15, 2020
@joshdover joshdover requested a review from a team as a code owner September 15, 2020 22:03
@joshdover joshdover requested a review from a team September 15, 2020 22:03
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform (Team:Platform)

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Build metrics

distributable file count

id value diff baseline
default 45572 +3 45569

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

Copy link
Contributor

@pgayvallet pgayvallet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Comment on lines +43 to +50
interface EmailSettingData {
xpack: { default_admin_email: string | null };
}

export interface KibanaSettingsCollector extends Collector<EmailSettingData | undefined> {
getEmailValueStructure(email: string | null): EmailSettingData;
}

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Be careful when backporting this, there is a difference between master and 7.x in the getEmailValueStructure implementation (the PR does not impact this so it should be fine, but just saying)

Copy link
Contributor

@chrisronline chrisronline left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Tested it with MB monitoring and works great

@joshdover joshdover merged commit b3aabe9 into elastic:master Sep 16, 2020
@joshdover joshdover deleted the status/api-settings branch September 16, 2020 20:24
joshdover added a commit to joshdover/kibana that referenced this pull request Sep 16, 2020
# Conflicts:
#	docs/developer/plugin-list.asciidoc
#	x-pack/plugins/monitoring/server/kibana_monitoring/collectors/get_settings_collector.ts
#	x-pack/plugins/xpack_legacy/kibana.json
#	x-pack/plugins/xpack_legacy/server/plugin.ts
pgayvallet pushed a commit that referenced this pull request Sep 17, 2020
* Migrate /api/settings to KP (#77554)

# Conflicts:
#	docs/developer/plugin-list.asciidoc
#	x-pack/plugins/monitoring/server/kibana_monitoring/collectors/get_settings_collector.ts
#	x-pack/plugins/xpack_legacy/kibana.json
#	x-pack/plugins/xpack_legacy/server/plugin.ts

* Fix lint

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Legacy Removal Issues related to removing legacy Kibana release_note:skip Skip the PR/issue when compiling release notes Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v7.10.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migrate /api/settings route to Kibana platform
5 participants