[Write restricted dashboards] Implements import and export changes by jeramysoucy · Pull Request #228416 · elastic/kibana

jeramysoucy · 2025-07-17T10:32:20Z

Summary

This PR implements changes to support import and export of saved objects that support access control features - namely, "write-restricted" dashboards (formerly "read-only" dashboards).

This effort is broken down into 2 phases:

Phase 1

Import will not apply the access control metadata from the imported file. This metadata contains the owner and access mode for the object. Instead, any new objects (that support access control) created as a result of import will be owned by the importing user and will be in default mode. If there is no active user profile (import called via API), the object will be created with no access control metadata (no owner or mode), but this can be assigned later by an admin. Any objects being overwritten as a result of import will maintain existing ownership and mode, but this can be changed later by the owner or an admin if needed.

Phase 2

Import will support applying the access control metadata from the imported file, but only for "Admin" users (users with the manage_access_control privilege). Admins will be able to specify an option to enable this behavior. If there is no access control metadata in the file for an existing object that will be overwritten, it will maintain existing ownership and mode.

This PR handles Phase 1, and Phase 2 will be handled in a follow-up effort.

Feature Flag Note

The changes here do not check the savedObjects.enableAccessControl config feature flag. The reasoning is that we still want to intercept unexpected access control metadata that may be present in export/import files and reject the import for any applicable objects. Alternatively, we could check the feature flag, and if disabled, always strip any incoming access control metadata.

Details

Import

Import relies on existing saved object bulk create functionality, which is handled by #224411 and #238468. Prior to bulk create, the import operation filters invalid objects and responds with this information to surface in the UI. Bulk create already handles object ID clashes and authorization for overwriting access control objects.

When importing objects with access control, the access control metadata from the import file will be ignored in order to preserve the owner and access mode for any existing objects being overwritten.

Access control requires some new filtering capability -

In Phase 1 (this phase) objects that should not include access control metadata
In Phase 2, objects missing required parts of access control metadata (only needed when we implement support for admins to import access control metadata - phase 2)

Since Phase 1 does not support importing access control metadata, this metadata will be stripped from incoming objects via another transform. Because of that, the filter transform is not critical in Phase 1, however, it implements the baseline for filtering needed in Phase 2, so it was worth staging here.

To achieve the filtering and stripping, I added the ability to set "access control transforms" with the saved object service. I created an import transform factory that will create a filter stream and a map streams (the transforms). This factory is set in the saved objects service and passed to the of SavedObjectsImporter constructor. This loosely follows the paradigm used to set the saved object repository extensions.

The filter stream handles all of the filtering of invalid objects, specific to access control, while the map stream handles removal of access control metadata (in Phase 1 for all users, in Phase 2 for non-admin users or when an admin has not specified the option to import access control metadata).

The end result - if the factory is defined, the import transform streams are generated during import, and executed inline with the other filter streams during the import process. After the invalid access control objects are filtered out, we rely on the bulk create operation to handle the rest.

Export

Originally during export we had planned to strip the access control metadata, but the design was revised. Keeping access control metadata in the export files means that they will contain everything necessary for import after Phase 2. Because of this, not export transforms are currently required.

We could implement a transform to strip the access control metadata when the access control feature flag is disabled, but this is not necessary - the additional metadata is not harmful or affective in Phase 1. We do not expect objects to contain metadata until the feature flag is enabled, and we do not expect the flag to be toggled back and forth.

Testing

This PR include both unit and integration tests for import, export, and resolve import errors APIs.

Risk

This functionality will sit behind a feature flag (to be implemented). If the feature is disabled, the transforms will not get set with the saved object service, leaving import and export to function as they did prior to this PR - verified by the existing suites of unit and integration tests.

Known issue

If an export file contains access control metadata and is imported when the feature flag is disabled, import will surface an error for each object that contains the metadata, stating that the object contains unexpected metadata. While we do not expect this to happen, if it ever does, removing the metadata from an export file is fairly simple and mitigates the issue.

Approach

As an alternative, the transforms can be moved inline with the rest of the importer and exporter codebase without significant effort.

…dashboards-crud-api

jeramysoucy · 2025-10-31T10:36:25Z

x-pack/platform/plugins/shared/security/server/saved_objects/access_control_transforms.ts

+} from '@kbn/core-saved-objects-server';
+import { createFilterStream, createMapStream } from '@kbn/utils';
+
+export function getImportTransformsFactory(): AccessControlImportTransformsFactory {


Opted to leave this as a factory to support phase 2, when we might need to pass in security functions/services again.

jeramysoucy · 2025-10-31T15:32:46Z

@SiddharthMantri The CI failure was just the post-build failure. All tests passed 🎉

TinaHeiligers · 2025-11-09T18:28:34Z

...ckages/saved-objects/import-export-server-internal/src/export/saved_objects_exporter.test.ts

      );
    });
+
+    // describe('access control', () => {


see my previous comment on removing data on export

src/core/packages/saved-objects/common/src/saved_objects_imports.ts

elena-shostak · 2025-11-12T10:55:03Z

...packages/saved-objects/import-export-server-internal/src/import/lib/collect_saved_objects.ts

      });
      return false;
    }),
+    ...(accessControlTransforms?.filterStream ? [accessControlTransforms.filterStream] : []),


since we are passing it down to a function, isn't it the same if we pass it just as is?

Suggested change

...(accessControlTransforms?.filterStream ? [accessControlTransforms.filterStream] : []),

accessControlTransforms?.filterStream

...([]) -> will end up as undefined passed to a function

I think there's a type mismatch when passed as just accessControlTransforms?.filterStream as the stream promise function is expecting the resolve value to have an iterator. Example error:

I thought of doing something like below to maybe improve readability but not sure if it makes sense. What do you think?

const optionalStream = <T>(stream: T | undefined): T[] => ...( stream ? [stream] : [] ) ; // ... optionalStream(accessControlTransforms?.filterStream), optionalStream(accessControlTransforms?.mapStream),

we can then leave it as it is right now 👍 no need to change

We're kinda blind to implementation changes with the factory function, and spreading unknowns makes it worse. We can cover some of the unknowns with testing. Maybe wrapping with some validation checks might be better in the long run. Let's mark that for Phase 2.

elena-shostak

Great job! left a couple of nits/questions I wanted to clarify before merging

SiddharthMantri · 2025-11-12T12:40:37Z

@elasticmachine merge upstream

…rt-export

elasticmachine · 2025-11-12T13:32:55Z

💔 Build Failed

Buildkite Build
Commit: 102edf7

Failed CI Steps

Metrics [docs]

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
`@kbn/core-saved-objects-api-server`	25	26	+1
`@kbn/core-saved-objects-common`	41	42	+1
`@kbn/core-saved-objects-server`	148	156	+8
total			+10

Public APIs missing exports

Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.

id	before	after	diff
`@kbn/core`	924	927	+3

Unknown metric groups

API count

id	before	after	diff
`@kbn/core-saved-objects-api-server`	410	411	+1
`@kbn/core-saved-objects-common`	74	76	+2
`@kbn/core-saved-objects-server`	622	631	+9
total			+12

History

cc @SiddharthMantri @jeramysoucy

dplumlee

Rule management changes LGTM, thanks @jeramysoucy!

dplumlee · 2025-11-12T21:22:38Z

...on/server/lib/detection_engine/rule_management/logic/import/action_connectors/utils/index.ts

Reading through the info on this and the code, I don't see rule actions as being supported for access based controls (at least for now, correct me if I'm wrong) so don't think this is necessarily reachable, but good to have this for future proofing errors.

TinaHeiligers

Almost done reviewing, there's a few things I want to get your thoughts on before doing one more round.

"If an export file contains access control metadata and is imported when the feature flag is disabled, import will surface an error for each object that contains the metadata, stating that the object contains unexpected metadata. While we do not expect this to happen, if it ever does, removing the metadata from an export file is fairly simple and mitigates the issue."

I can almost 100% guarantee this will happen. We have no control over where the exported saved objects come from.

src/core/packages/saved-objects/api-server-internal/src/lib/apis/create.test.ts

TinaHeiligers · 2025-11-14T00:15:49Z

...packages/saved-objects/import-export-server-internal/src/import/lib/collect_saved_objects.ts

      });
      return false;
    }),
+    ...(accessControlTransforms?.filterStream ? [accessControlTransforms.filterStream] : []),


We're kinda blind to implementation changes with the factory function, and spreading unknowns makes it worse. We can cover some of the unknowns with testing. Maybe wrapping with some validation checks might be better in the long run. Let's mark that for Phase 2.

TinaHeiligers · 2025-11-14T01:20:15Z

...ckages/saved-objects/import-export-server-internal/src/export/saved_objects_exporter.test.ts

+      });
+
+      test('does not apply the access control transform to types that do not support access control', async () => {
+        // const accessControlExportTransform: SavedObjectsExportTransform = (ctx, objects) => {


uncomment the transform. Without it, we're not actually testing what it claims to.

TinaHeiligers · 2025-11-14T01:20:42Z

...ckages/saved-objects/import-export-server-internal/src/export/saved_objects_exporter.test.ts

+    // Unskip after: https://github.com/elastic/kibana/issues/242671
+    describe.skip('access control', () => {
+      test('applies the access control transform to supporting types if defined', async () => {
+        // const accessControlExportTransform: SavedObjectsExportTransform = (ctx, objects) => {


TinaHeiligers · 2025-11-14T01:20:54Z

...ckages/saved-objects/import-export-server-internal/src/export/saved_objects_exporter.test.ts

+          logger,
+          savedObjectsClient,
+          typeRegistry,
+          // accessControlExportTransform,


TinaHeiligers · 2025-11-14T01:36:45Z

src/core/packages/saved-objects/server-internal/src/saved_objects_service.test.ts

+          const setup = await soService.setup(createSetupDeps());
+
+          const accessControlTransforms: SavedObjectsAccessControlTransforms = {
+            // exportTransform: jest.fn(),


remove or comment on why exportTransform is commented out

TinaHeiligers · 2025-11-14T01:49:21Z

x-pack/platform/plugins/shared/security/server/saved_objects/access_control_transforms.ts

+      const typeSupportsAccessControl = typeRegistry.supportsAccessControl(obj.type);
+
+      if (typeSupportsAccessControl && obj.accessControl) {
+        delete obj.accessControl;


How are we thinking about surfacing this to users?

I'm thinking along the lines of a warning to either proceed or cancel the import.

TinaHeiligers · 2025-11-15T01:27:33Z

src/core/packages/saved-objects/server/src/import.ts

  objects: Array<SavedObject<T>>
 ) => SavedObjectsImportHookResult | Promise<SavedObjectsImportHookResult>;
+
+export interface AccessControlImportTransforms {


nit: Missing .ts docs ;-)

TinaHeiligers

Great work!
Phase 1 changes look ok, I left a few comments and nits but nothing blocking.
Tested locally by running the ftr server for the spaces API integration test, and used SOM import/export to validate the behavior.

TinaHeiligers · 2025-11-15T01:29:39Z

src/core/packages/saved-objects/server/src/import.ts

+  mapStream: Transform;
+}
+
+export type AccessControlImportTransformsFactory = (


nit: Missing .ts docs ;-)

TinaHeiligers · 2025-11-15T02:26:13Z

...core/packages/saved-objects/import-export-server-internal/src/import/import_saved_objects.ts

    supportedTypes,
    managed,
+    typeRegistry,
+    createAccessControlImportTransforms,


Handling access control in the importStateMap means that the ownership will already be decided by the time the objects are passed to createSavedObjects, which will work for Phase 1. However, the ownership will become tricky if we want to offer an intermittent step to change ownership per object being imported. Just a thought for later on.

Closes elastic/kibana-team#808 The respective teams have been raising PRs against this feature branch. Approved PRs merged so far: - #221916 - #224411 - #239973 - #241101 - #238468 - #233552 - #228416 - #241168 - #244746 - #244830 ## Summary This pull request overhauls the saved object management workflow by introducing the concept of ownership for SOs - specifically enabled for dashboards only at the moment. Owners and administrators can now control a new write-restricted flag on their objects, allowing them to keep work draft/uneditable state before publishing. This change enables users to define who can modify shared objects, providing a crucial capability to manage and share dashboards. ## Release note Kibana Dashboards now support ownership and "write_restricted" mode. Users can now keep dashboards publicly editable or in a write-restricted state until they are ready to publish, giving them more control over who can edit their dashboards, regardless of broader space permissions. ## How to test ### Serverless Please reach out to me via slack or in the project channel (#read-only-dashboards) to be invited to the serverless environment where this feature has been enabled. ### Local - Clone this PR - Enable the feature by editing kibana.yml to include ``` savedObjects.enableAccessControl: true ``` - Start ES and Kibana as you would - Once started, seed Kibana with sample data. This should create a few dashboards. - Navigate to dashboards and create a new one. - In the share modal, change the view mode `Everybody in the space Can View`, <img width="500" height="410" alt="image" src="https://github.com/user-attachments/assets/b895442f-cce3-41a6-8b47-d206a9afbf43" /> - Now create a new role which grants access to indices and dashboards all. Create a new user and then assign that role to the newly created user. <img width="500" height="410" alt="image" src="https://github.com/user-attachments/assets/dd5251e1-a3b5-41a8-abc1-7e67399d65d2" /> - Login as the new user and navigate to the dashboard you had initially set as `Can view`. You'll see that you're not able to edit the dashboard and a warning like <img width="500" height="410" alt="Screenshot 2025-11-28 at 12 30 50" src="https://github.com/user-attachments/assets/1f71ccc7-9dc6-4a68-9a2c-540aa74e4f03" /> ### Local (2nd option) You can also follow the instructions in #224411 that detail how to use the funtional test runner to test this using the test plugin created for this feature. ### Risk matrix - What happens when your feature is used in a non-default space or a custom space? Works as expected - What happens when there are multiple Kibana nodes using the same Elasticsearch cluster? Does not depend on functionality of kibana nodes - What happens when a plugin you depend on is disabled? Changes are in core and security - both are always available - What happens when a feature you depend on is disabled? No dependency - What happens when a third party integration you depend on is not responding? No third party inregration - Does the feature work in Elastic Cloud? Yes - Does the feature create a setting that needs to be exposed, or configured differently than the default, on the Elastic Cloud? No - Is there a significant performance impact that may affect Cloud Kibana instances? No - Does your feature need to be aware of running in a container? No - Does the feature Work with security disabled, or fails gracefully? If disabled, fails gracefully. - Are there performance risks associated with your feature? No - Could this cause memory to leak in either the browser or server? No - Will your feature still work if Kibana is run behind a reverse proxy? Yes - Does your feature affect other plugins? No, other plugins could choose to use it if registering a SO with ownable types - Are migrations handled gracefully? Does the feature affect old indices or saved objects? Yes, migrations taken care of. - Are you using any technologies, protocols, techniques, conventions, libraries, NPM modules, etc. that may be new or unprecedented in Kibana? No --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co> Co-authored-by: Aleh Zasypkin <aleh.zasypkin@gmail.com> Co-authored-by: Christiane (Tina) Heiligers <christiane.heiligers@elastic.co> Co-authored-by: Krzysztof Kowalczyk <krzysztof.kowalczyk@elastic.co> Co-authored-by: Gerard Soldevila <gerard.soldevila@elastic.co>

Closes elastic/kibana-team#808 The respective teams have been raising PRs against this feature branch. Approved PRs merged so far: - elastic#221916 - elastic#224411 - elastic#239973 - elastic#241101 - elastic#238468 - elastic#233552 - elastic#228416 - elastic#241168 - elastic#244746 - elastic#244830 ## Summary This pull request overhauls the saved object management workflow by introducing the concept of ownership for SOs - specifically enabled for dashboards only at the moment. Owners and administrators can now control a new write-restricted flag on their objects, allowing them to keep work draft/uneditable state before publishing. This change enables users to define who can modify shared objects, providing a crucial capability to manage and share dashboards. ## Release note Kibana Dashboards now support ownership and "write_restricted" mode. Users can now keep dashboards publicly editable or in a write-restricted state until they are ready to publish, giving them more control over who can edit their dashboards, regardless of broader space permissions. ## How to test ### Serverless Please reach out to me via slack or in the project channel (#read-only-dashboards) to be invited to the serverless environment where this feature has been enabled. ### Local - Clone this PR - Enable the feature by editing kibana.yml to include ``` savedObjects.enableAccessControl: true ``` - Start ES and Kibana as you would - Once started, seed Kibana with sample data. This should create a few dashboards. - Navigate to dashboards and create a new one. - In the share modal, change the view mode `Everybody in the space Can View`, <img width="500" height="410" alt="image" src="https://github.com/user-attachments/assets/b895442f-cce3-41a6-8b47-d206a9afbf43" /> - Now create a new role which grants access to indices and dashboards all. Create a new user and then assign that role to the newly created user. <img width="500" height="410" alt="image" src="https://github.com/user-attachments/assets/dd5251e1-a3b5-41a8-abc1-7e67399d65d2" /> - Login as the new user and navigate to the dashboard you had initially set as `Can view`. You'll see that you're not able to edit the dashboard and a warning like <img width="500" height="410" alt="Screenshot 2025-11-28 at 12 30 50" src="https://github.com/user-attachments/assets/1f71ccc7-9dc6-4a68-9a2c-540aa74e4f03" /> ### Local (2nd option) You can also follow the instructions in elastic#224411 that detail how to use the funtional test runner to test this using the test plugin created for this feature. ### Risk matrix - What happens when your feature is used in a non-default space or a custom space? Works as expected - What happens when there are multiple Kibana nodes using the same Elasticsearch cluster? Does not depend on functionality of kibana nodes - What happens when a plugin you depend on is disabled? Changes are in core and security - both are always available - What happens when a feature you depend on is disabled? No dependency - What happens when a third party integration you depend on is not responding? No third party inregration - Does the feature work in Elastic Cloud? Yes - Does the feature create a setting that needs to be exposed, or configured differently than the default, on the Elastic Cloud? No - Is there a significant performance impact that may affect Cloud Kibana instances? No - Does your feature need to be aware of running in a container? No - Does the feature Work with security disabled, or fails gracefully? If disabled, fails gracefully. - Are there performance risks associated with your feature? No - Could this cause memory to leak in either the browser or server? No - Will your feature still work if Kibana is run behind a reverse proxy? Yes - Does your feature affect other plugins? No, other plugins could choose to use it if registering a SO with ownable types - Are migrations handled gracefully? Does the feature affect old indices or saved objects? Yes, migrations taken care of. - Are you using any technologies, protocols, techniques, conventions, libraries, NPM modules, etc. that may be new or unprecedented in Kibana? No --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co> Co-authored-by: Aleh Zasypkin <aleh.zasypkin@gmail.com> Co-authored-by: Christiane (Tina) Heiligers <christiane.heiligers@elastic.co> Co-authored-by: Krzysztof Kowalczyk <krzysztof.kowalczyk@elastic.co> Co-authored-by: Gerard Soldevila <gerard.soldevila@elastic.co>

SiddharthMantri and others added 30 commits June 28, 2025 18:08

incomplete implementation

009ae43

update tests

40bac7e

Update access control service

6e2a755

enforceAccessControl checls

40e0138

remove unused params

132151f

Add authzChangeAccessMode

8ecbf03

fix verbs

1ad2ac8

Update unit tests

3846ea5

update ftr

6bce6da

Update extension unit tests

e035423

Update APIs, improve flow

0a9f36e

implement saved objects access mode change and refactor ownership change

8087054

fix security extension tests

f12080b

update mocks

d89ed27

restore defaults

cc3abe8

update changeaccessControl code

184ae08

[CI] Auto-commit changed files from 'node scripts/generate codeowners'

24553c1

Fix types

39462dc

update tsdocs

a288781

update test

e501ceb

fix types

069f03f

Update types

8714845

update find test

eaf6b7b

Merge branch 'security/read-only-dashboards' into security/read-only-…

b2b9f5e

…dashboards-crud-api

update tests

8c1ffa1

use set

7d20fc9

update tests

5cba6f3

update test types

de063f6

update changes to tests

e73b3a9

remove type field

4f793b6

Fixes more merge issues and removes comments

e139511

jeramysoucy commented Oct 31, 2025

View reviewed changes

Fixes type check issues, removed unneeded export transform option

fcaf956

SiddharthMantri assigned SiddharthMantri and jeramysoucy Oct 31, 2025

SiddharthMantri added 3 commits October 31, 2025 14:23

fix create jest test

26516fe

fix jest tests with access control import transforms

3bf99c6

remove unused types

7831a51

elena-shostak self-requested a review November 3, 2025 12:10

TinaHeiligers reviewed Nov 9, 2025

View reviewed changes

elena-shostak reviewed Nov 12, 2025

View reviewed changes

SiddharthMantri added 4 commits November 12, 2025 12:19

Add GH issue to track commented features

d92ce55

use test skips

b358a76

fix type error

7b9aae1

fix types, add link to GH issue

5a4e798

Merge branch 'security/read-only-dashboards' into read-only-dash-impo…

102edf7

…rt-export

dplumlee approved these changes Nov 12, 2025

View reviewed changes

TinaHeiligers reviewed Nov 14, 2025

View reviewed changes

This comment was marked as duplicate.

Sign in to view

TinaHeiligers reviewed Nov 15, 2025

View reviewed changes

TinaHeiligers approved these changes Nov 15, 2025

View reviewed changes

SiddharthMantri requested a review from elena-shostak November 17, 2025 09:07

elena-shostak approved these changes Nov 17, 2025

View reviewed changes

SiddharthMantri merged commit a74e038 into elastic:security/read-only-dashboards Nov 17, 2025
10 of 12 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Write restricted dashboards] Implements import and export changes#228416

[Write restricted dashboards] Implements import and export changes#228416
SiddharthMantri merged 309 commits intoelastic:security/read-only-dashboardsfrom
jeramysoucy:read-only-dash-import-export

jeramysoucy commented Jul 17, 2025 •

edited

Loading

jeramysoucy Oct 31, 2025

jeramysoucy commented Oct 31, 2025

TinaHeiligers Nov 9, 2025

Uh oh!

elena-shostak Nov 12, 2025

SiddharthMantri Nov 12, 2025

elena-shostak Nov 12, 2025 •

edited

Loading

TinaHeiligers Nov 14, 2025

elena-shostak left a comment

SiddharthMantri commented Nov 12, 2025

elasticmachine commented Nov 12, 2025 •

edited

Loading

API count

dplumlee left a comment

dplumlee Nov 12, 2025 •

edited

Loading

TinaHeiligers left a comment

Uh oh!

TinaHeiligers Nov 14, 2025

TinaHeiligers Nov 14, 2025

TinaHeiligers Nov 14, 2025

TinaHeiligers Nov 14, 2025

TinaHeiligers Nov 14, 2025

TinaHeiligers Nov 14, 2025

This comment was marked as duplicate.

Uh oh!

TinaHeiligers Nov 15, 2025 •

edited

Loading

TinaHeiligers left a comment •

edited

Loading

TinaHeiligers Nov 15, 2025 •

edited

Loading

TinaHeiligers Nov 15, 2025 •

edited

Loading

Uh oh!

Labels

7 participants

	...(accessControlTransforms?.filterStream ? [accessControlTransforms.filterStream] : []),
	accessControlTransforms?.filterStream

Conversation

jeramysoucy commented Jul 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Phase 1

Phase 2

Feature Flag Note

Details

Import

Export

Testing

Risk

Known issue

Approach

Choose a reason for hiding this comment

jeramysoucy commented Oct 31, 2025

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Choose a reason for hiding this comment

elena-shostak Nov 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Choose a reason for hiding this comment

elena-shostak left a comment

Choose a reason for hiding this comment

SiddharthMantri commented Nov 12, 2025

elasticmachine commented Nov 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

💔 Build Failed

Failed CI Steps

Metrics [docs]

Public APIs missing comments

Public APIs missing exports

API count

History

dplumlee left a comment

Choose a reason for hiding this comment

dplumlee Nov 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

TinaHeiligers left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

This comment was marked as duplicate.

Uh oh!

TinaHeiligers Nov 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

TinaHeiligers left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

TinaHeiligers Nov 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

TinaHeiligers Nov 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Labels

7 participants

jeramysoucy commented Jul 17, 2025 •

edited

Loading

elena-shostak Nov 12, 2025 •

edited

Loading

elasticmachine commented Nov 12, 2025 •

edited

Loading

dplumlee Nov 12, 2025 •

edited

Loading

TinaHeiligers Nov 15, 2025 •

edited

Loading

TinaHeiligers left a comment •

edited

Loading

TinaHeiligers Nov 15, 2025 •

edited

Loading

TinaHeiligers Nov 15, 2025 •

edited

Loading