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

[Telemetry] schema check throw on missing schema #75750

Merged
merged 3 commits into from
Aug 24, 2020

Conversation

Bamieh
Copy link
Member

@Bamieh Bamieh commented Aug 24, 2020

Update schemas and add a check to throw when schemas change.

@Bamieh Bamieh added v8.0.0 release_note:skip Skip the PR/issue when compiling release notes Team:KibanaTelemetry v7.10.0 labels Aug 24, 2020
@Bamieh Bamieh requested a review from a team as a code owner August 24, 2020 13:10
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-telemetry (Team:KibanaTelemetry)

Comment on lines +35 to +43
if (root.esMappingDiffs.length && throwOnDiff) {
throw Error(
`The following changes must be persisted in ${fullPath} file. Use '--fix' to update.\n${JSON.stringify(
differences,
null,
2
)}`
);
}
Copy link
Member

Choose a reason for hiding this comment

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

I've got the same question as in #75747 (comment): Are devs in charge of running these changes themselves (maintaining the merged-schemas JSON files) and we simply accept them? Or are we supposed to run the extract after FF to see all the changes at once?

Copy link
Member Author

Choose a reason for hiding this comment

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

Devs run the --fix to update the json files, and we approve them since we are the owners of that file. After FF we run the extract to grab json file to see all the additions between releases similiar to what we do with i18n.

Copy link
Member

Choose a reason for hiding this comment

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

Does extract generate another JSON file? I thought it was the same one. But it that's the intended process. LGTM 👍

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Build metrics

✅ unchanged

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

@Bamieh Bamieh merged commit ec7578c into elastic:master Aug 24, 2020
@Bamieh Bamieh deleted the telemetry/throw_on_missing_schema branch August 24, 2020 15:01
Bamieh added a commit that referenced this pull request Aug 24, 2020
* [Telemetry] schema check throw on missing schema (#75750)

* update schema for 7.x
@lukeelmers lukeelmers added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Oct 1, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Telemetry 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.

5 participants