-
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
[Automatic Import] rename plugin to automatic import #207325
[Automatic Import] rename plugin to automatic import #207325
Conversation
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
buildkite test this |
The api docs offenses were already present with the old plugin's name. I have created a follow-up issue to fix them #208113 |
deb8565
to
edaa558
Compare
Is this strictly a rename? Do we know why there's +1.1mb on async bundles? |
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 changes LGTM 🚀
@jbudz |
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.
x-pack/test/tsconfig.json lgtm
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.
LGTM
@@ -5,6 +5,7 @@ pageLoadAssetSize: | |||
aiops: 32733 | |||
alerting: 106936 | |||
apm: 64385 | |||
automaticImport: 25433 |
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.
Why is this different from the original one?
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 updated it by running the command node scripts/build_kibana_platform_plugins.js --update-limits
. Is there another process to update this file?
FYI the build fails because of |
I suggest we add a release note about the rename. |
d3b0817
to
46889e6
Compare
* under the `allowedExperimentalValues` object | ||
* | ||
* @example | ||
* xpack.integration_assistant.enableExperimental: | ||
* xpack.automatic_import.enableExperimental: |
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.
How confident are we that no customers have xpack.integration_assistant
set? If any cluster has a xpack.integration_assistant.*
config option set then Kibana would fail to start once they upgrade.
If that's a possibility we might need to keep an xpack.integration_assistant
plugin which has only a config deprecation or look at other ways to avoid an upgrade failure.
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 we had
xpack.integration_assistant.enabled: true xpack.integration_assistant.enableExperimental: ['generateCel']
Of which, xpack.integration_assistant.enabled
is default enabled on all clusters.. And xpack.integration_assistant.enableExperimental
is introduced as internal only.
But as you mentioned it might be better to keep an xpack.integration_assistant plugin which has only a config deprecation
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.
If I think more , this config xpack.integration_assistant.enabled
is disabled for few customers, which means this should be deprecated in all 8.x deployments.
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 forgot we had the ability to do this without keeping the old plugin by using renameFromRoot
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've added renameFromRoot
for the 2 config options and tested with having
xpack.integration_assistant.enabled: true
xpack.automatic_import.enabled: true
xpack.automatic_import.enableExperimental: ['generateCel']
xpack.integration_assistant.enableExperimental: ['generateCel']
in kibana.dev.yml
. No issues
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.
May be figure out a way to test upgrade with existing deployment and upgrade to changes in your PR.
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.
Changes in test/plugin_functional/test_suites/core_plugins/rendering.ts LGTM
e5d9f99
to
c5aeadc
Compare
Pinging @elastic/security-scalability (Team:Security-Scalability) |
…:haetamoudi/kibana into 197621-rename-plugin-to-automatic_import
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 have to say that the name of the new automaticImport
plugin is rather vague. I miss the integration noun somewhere, this name doesn't say anything about what it is that is automatically imported. It's too generic IMO.
But anyway, code LGTM.
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.
Core changes lgtm and the config deprecation should ensure we don't block upgrades
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Public APIs missing exports
Page load bundle
Unknown metric groupsAPI count
async chunk count
ESLint disabled in files
ESLint disabled line counts
miscellaneous assets size
Total ESLint disabled count
History
cc @haetamoudi |
Summary
Rename
integration-assistant
plugin toautomatic-import
. Github issueOutdated PR to rename plugin,
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breaking
label should be applied in these situations.release_note:*
label is applied per the guidelinesCommands executed
node scripts/i18n_check --fix
node scripts/lint_ts_projects
node scripts/generate codeowners
node scripts/build_plugin_list_docs
node scripts/build_kibana_platform_plugins.js --update-limits
Testing
automatic-import
plugin ✅Follow-up
Once the PR is merged, the following dashboards will need to be updated to reflect the Telemetry keys changes:
Looker: https://lookerstudio.google.com/u/0/reporting/5eb00475-46bc-4c57-93da-5b2d00058c8a/page/p_t7j5zagckd?pli=1
Stack Telemetry: https://stack-telemetry.elastic.dev/s/securitysolution/app/dashboards#/view/e7662c09-eedb-49aa-9615-0600fcb[…]60000),time:(from:now-30d%2Fd,to:now))