Skip to content

Conversation

@Kiryous
Copy link
Contributor

@Kiryous Kiryous commented Jul 24, 2025

Summary

Before

422K workflowsManagement.plugin.js

After

4.1K workflowsManagement.plugin.js

Root cause

  1. Direct export of the WorkflowExecution component added 336kb
    https://github.com/Kiryous/kibana/blob/main/src/platform/plugins/shared/workflows_management/public/index.ts#L18
  2. import of generateYamlSchemaFromConnectors in common/index added another 82kb https://github.com/Kiryous/kibana/blob/5d05dd06aa40b75885cb5496f5af3ae825b1f773/src/platform/plugins/shared/workflows_management/common/index.ts#L10
    Without these, the plugin bundle size is modest 4.1K

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

  • Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
  • Documentation was added for features that require explanation or tutorials
  • Unit or functional tests were updated or added to match the most common scenarios
  • If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
  • This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
  • Flaky Test Runner was used on any tests changed
  • The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
  • Review the backport guidelines and apply applicable backport:* labels.

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

@Kiryous Kiryous added backport:skip This PR does not require backporting release_note:skip Skip the PR/issue when compiling release notes labels Jul 24, 2025
@Kiryous Kiryous marked this pull request as ready for review July 24, 2025 12:15
@Kiryous Kiryous requested review from a team as code owners July 24, 2025 12:15
Copy link
Contributor

@talboren talboren left a comment

Choose a reason for hiding this comment

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

lgtm

@tinnytintin10 tinnytintin10 added the Team:One Workflow Team label for One Workflow (Workflow automation) label Jul 29, 2025
# Conflicts:
#	src/platform/plugins/shared/workflows_management/common/index.ts
#	src/platform/plugins/shared/workflows_management/public/pages/workflow_detail/index.tsx
#	src/platform/plugins/shared/workflows_management/server/workflows_management/workflows_management_service.ts
@Kiryous Kiryous requested a review from a team as a code owner August 4, 2025 08:04
…ting/log_threshold/components/expression_editor/criterion.tsx` eslint autofix
@Kiryous Kiryous removed the request for review from a team August 4, 2025 08:09
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
workflowsManagement 372 374 +2

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id before after diff
workflowsManagement 20 17 -3

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
workflowsManagement 32.7KB 451.4KB ⚠️ +418.7KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
workflowsManagement 422.0KB 4.3KB -417.7KB
Unknown metric groups

API count

id before after diff
workflowsManagement 20 18 -2

async chunk count

id before after diff
workflowsManagement 1 3 +2

History

@Kiryous Kiryous merged commit ff36057 into elastic:main Aug 4, 2025
12 checks passed
szaffarano pushed a commit to szaffarano/kibana that referenced this pull request Aug 5, 2025
## Summary

### Before
422K workflowsManagement.plugin.js

### After
4.1K workflowsManagement.plugin.js

### Root cause
  1. Direct export of the `WorkflowExecution` component added 336kb

https://github.com/Kiryous/kibana/blob/main/src/platform/plugins/shared/workflows_management/public/index.ts#L18
2. import of `generateYamlSchemaFromConnectors` in common/index added
another 82kb
https://github.com/Kiryous/kibana/blob/5d05dd06aa40b75885cb5496f5af3ae825b1f773/src/platform/plugins/shared/workflows_management/common/index.ts#L10
 Without these, the plugin bundle size is modest 4.1K

### Checklist

Check the PR satisfies following conditions. 

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [ ] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...
delanni pushed a commit to delanni/kibana that referenced this pull request Aug 5, 2025
## Summary

### Before
422K workflowsManagement.plugin.js

### After
4.1K workflowsManagement.plugin.js

### Root cause
  1. Direct export of the `WorkflowExecution` component added 336kb

https://github.com/Kiryous/kibana/blob/main/src/platform/plugins/shared/workflows_management/public/index.ts#L18
2. import of `generateYamlSchemaFromConnectors` in common/index added
another 82kb
https://github.com/Kiryous/kibana/blob/5d05dd06aa40b75885cb5496f5af3ae825b1f773/src/platform/plugins/shared/workflows_management/common/index.ts#L10
 Without these, the plugin bundle size is modest 4.1K

### Checklist

Check the PR satisfies following conditions. 

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [ ] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...
@wildemat wildemat mentioned this pull request Aug 7, 2025
10 tasks
@Kiryous Kiryous deleted the fix/13318-workflows-management-plugin-bundle branch August 11, 2025 09:47
NicholasPeretti pushed a commit to NicholasPeretti/kibana that referenced this pull request Aug 18, 2025
## Summary

### Before
422K workflowsManagement.plugin.js

### After
4.1K workflowsManagement.plugin.js

### Root cause
  1. Direct export of the `WorkflowExecution` component added 336kb

https://github.com/Kiryous/kibana/blob/main/src/platform/plugins/shared/workflows_management/public/index.ts#L18
2. import of `generateYamlSchemaFromConnectors` in common/index added
another 82kb
https://github.com/Kiryous/kibana/blob/5d05dd06aa40b75885cb5496f5af3ae825b1f773/src/platform/plugins/shared/workflows_management/common/index.ts#L10
 Without these, the plugin bundle size is modest 4.1K

### Checklist

Check the PR satisfies following conditions. 

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [ ] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

### Identify risks

Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.

- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
- [ ] ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip This PR does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team:One Workflow Team label for One Workflow (Workflow automation) v9.2.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants