Page Comparison

1. Ensure that a separate subnet is attached to it with delegation (Microsoft.DBforPostgreSWL/flexibleServers and service endpoints Storage, KeyVault, SQL, and Web).

2. If using an existing Azure Database for Postgres Flexible Server Contributor role permission must be attached to managed identity on resource level to start/stop Postgres Flexible server through scheduling.

3. To use an externally created Flexible Server in deployments, use ARM templates the ARM template (FlexibleServerKyvosManagerRepository and FlexibleServerKyvosRepository) to create a Flexible Server that can be used in the deployments directly. OR, if you can also create Flexible Server version 13 (supported for both new deployments and upgrades) through Microsoft, then you need to complete the following steps. For more information about how to create Flexible Server, refer to Microsoft documentation.

   1. For Kyvos repository

      1. Database The database name must be delverepo.

      2. Username The username must be postgres

      3. Following The following tags are expected on the external repository:
         UsedBy - Kyvos
         ROLE - DATABASE
         LAYER - Metadata_Storage

   2. For Kyvos Manager repository

      1. Database name must be kmrepo.

      2. Username must be kmdbuser

      3. Following tags are expected on the external repository:
         UsedBy - Kyvos
         ROLE - DATABASE_KM
         LAYER - Metadata_Storage

...