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

[Dashboard] Deprecate Allow By Value Embeddables Setting #137219

Conversation

ThomThomson
Copy link
Contributor

Summary

The Allow By Value Embeddables setting was added as part of the Time to Visualize project. It was turned on by default in 7.12. This setting has been unused since, and is adding additional complexity to the dashboard code.

This PR doesn't delete the setting, but it does mark it as deprecated in the hopes that we can then check its usage by counting up occurrences in the telemetry under the key stack_stats.kibana.plugins.core.config.deprecatedKeys.unset

@TinaHeiligers

@ThomThomson ThomThomson added Feature:Dashboard Dashboard related features Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas labels Jul 26, 2022
@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

✅ unchanged

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

@@ -15,6 +15,9 @@ export const config: PluginConfigDescriptor<ConfigSchema> = {
allowByValueEmbeddables: true,
},
schema: configSchema,
deprecations: ({ deprecate }) => {
return [deprecate('allowByValueEmbeddables', '8.6.0', { level: 'warning' })];
Copy link
Contributor

Choose a reason for hiding this comment

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

👍

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks Tina! Just to confirm, this will make this setting show up in stack_stats.kibana.plugins.core.config.deprecatedKeys.unset when it is unset?

Copy link
Contributor

Choose a reason for hiding this comment

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

I believe so, yes.
cc @Bamieh please correct me if I'm wrong

Copy link
Member

@Bamieh Bamieh Aug 30, 2022

Choose a reason for hiding this comment

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

If i'm not mistaken the deprecate helper will only log a warning. I recommend using the unused helper for this config. it will not add telemetry insidestack_stats.kibana.plugins.core.config.deprecatedKeys.unset

This is the code for the deprecate helper:
https://github.com/elastic/kibana/blob/main/packages/kbn-config/src/deprecation/deprecation_factory.ts#L209

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hey @Bamieh, sorry for the late reply! Will the unused helper add telemetry? If not, is there a way we can do so? One of the main reasons for deprecating this is so we can see if any clusters are using it. It's unlikely that any are.

Will the unused helper throw warnings or errors on startup if a cluster happens to be configured with that key?

@ThomThomson
Copy link
Contributor Author

Closing this for now. Will look into this again in the future.

@ThomThomson ThomThomson closed this Jan 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Dashboard Dashboard related features Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants