Skip to content

Commit cf2daff

Browse files
committed
prettier
1 parent 3b024f9 commit cf2daff

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

content/docs/deploy/upgrading.mdx

+2
Original file line numberDiff line numberDiff line change
@@ -286,13 +286,15 @@ Your Pomerium Enterprise version should always match the same **minor version nu
286286
:::
287287

288288
To **upgrade** a Pomerium Enterprise deployment, we recommend that you:
289+
289290
1. First review the version-specific upgrade notes on this page for **both** Pomerium Core and Pomerium Enterprise for any changes that might pertain to your deployment. (If you're not sure, please don't hesitate to reach out and ask for clarification.)
290291
1. Take a database backup of the Pomerium Enterprise database.
291292
1. Upgrade Pomerium Core to the new version. For a replicated deployment, instances can be updated one at a time to avoid downtime.
292293
1. Upgrade Pomerium Enterprise to the new version.
293294
1. Verify that your deployment continues to behave as expected.
294295

295296
In case of trouble during the upgrade process, follow these steps to **roll back** to the previous version:
297+
296298
1. Stop Pomerium Enterprise.
297299
1. Restore the Pomerium Enterprise database from a backup taken before the upgrade.
298300
1. Downgrade Pomerium Core to the previous version.

0 commit comments

Comments
 (0)