# Migrations

#### Release v843

Please reach out if you are using the WARPSTREAM\_TABLEFLOW\_ASSUME\_ROLE\_ARN env var along with the prefix feature for Tableflow before upgrading. This version fixes the usage of the prefix query param in the bucket url, which changes where data is stored. We believe no customer is using the combination today but if you have doubts we can double check to make this migration safe.

#### Release v840

The `warpstream.tableflow_partition_offset_lag` metric has been renamed to `warpstream.tableflow_ingestion_offset_lag` and the `-tableflowClusterMetricsTagDenyList` flag or the `WARPSTREAM_TABLEFLOW_CLUSTER_METRICS_TAG_DENY_LIST` environment variable should be used to configure tags to omit from the Tableflow lag metrics. By default the `partition` tag will be omitted.

#### Release v802

If you are using the [AWS Glue integration in Tableflow](/warpstream/tableflow/catalogs-and-query-engines/aws-glue), two new actions are needed in your IAM policy:

* `glue:GetTableVersions`
* `glue:BatchDeleteTableVersion`

#### Release v793

If you are whitelisting the WarpStream control plane endpoint (like `metadata.default.us-east-1.warpstream.com`) you need to add additional endpoints before migrating. The exact format is:

```
<prefix>.metadata.<region>.<cloud_provider>.warpstream.com
```

With the following fields:

* `prefix` will be `alpha`, `beta` and `gamma` , meaning you need to whitelist 3 different values (always the 3 values, no matter what the region/cloud provider is)
* `region` is what you picked in the console UI or through the API, like `us-east-1` or `eastus`
* `cloud_provider` is the cloud provider of the region you pickred in the console UI or through the API. We support: `aws` / `gcp` / `azure`

Concretely let's say you picked `aws`/`us-east-1` in the console, you want to whitelist the 3 endpoints:

* `alpha.metadata.us-east-1.aws.warpstream.com`
* `beta.metadata.us-east-1.aws.warpstream.com`
* `gamma.metadata.us-east-1.aws.warpstream.com`