Skip to content

Commit

Permalink
address pr comments
Browse files Browse the repository at this point in the history
  • Loading branch information
efd6 committed Mar 2, 2025
1 parent f061396 commit 1c587ac
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions packages/entityanalytics_okta/_dev/build/docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,11 @@ This [Okta Entity Analytics](https://www.okta.com/) integration allows users to

This module has been tested against the Core Okta API version **v1**.

## Upgrading to v2 from v1
## Upgrading to v2 from v1 of the integration

In v2 of the integration the user and device data was split into separate data streams. The data ingested into your index will be the same but you may need to update device searches if you were using them.

**NOTE**: When you upgrade from v1 you will need to reconfigure the integration and enable it due to internal changes in the package.
**NOTE**: When you upgrade from v1 you will need to reconfigure the integration and enable it due to internal changes in the package. See [Resolve conflicts](https://www.elastic.co/guide/en/fleet/current/upgrade-integration.html#resolve-conflicts) in the Fleet documentation for details.

## Data streams

Expand Down
4 changes: 2 additions & 2 deletions packages/entityanalytics_okta/docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,11 @@ This [Okta Entity Analytics](https://www.okta.com/) integration allows users to

This module has been tested against the Core Okta API version **v1**.

## Upgrading to v2 from v1
## Upgrading to v2 from v1 of the integration

In v2 of the integration the user and device data was split into separate data streams. The data ingested into your index will be the same but you may need to update device searches if you were using them.

**NOTE**: When you upgrade from v1 you will need to reconfigure the integration and enable it due to internal changes in the package.
**NOTE**: When you upgrade from v1 you will need to reconfigure the integration and enable it due to internal changes in the package. See [Resolve conflicts](https://www.elastic.co/guide/en/fleet/current/upgrade-integration.html#resolve-conflicts) in the Fleet documentation for details.

## Data streams

Expand Down

0 comments on commit 1c587ac

Please sign in to comment.