Merge pull request #5481 from EnterpriseDB/release/2024-04-08a

Release/2024-04-08a

product_docs/docs/biganimal/release/administering_cluster/notifications.mdx

@@ -0,0 +1,60 @@
+---
+title: Notifications 
+---
+
+With BigAnimal, you can opt to get specific types of notifications and receive both in-app and email notifications.
+
+Different types of events are sent as notifications. These notifications are set at different levels and users with different roles can configure this notifications. This table provides the list of events sent as notifications grouped by different levels at which they can be set:
+
+| Level        | Event                                                                                            | Role                             | Subscription type    |
+|--------------|--------------------------------------------------------------------------------------------------|----------------------------------|--------------------- |
+| Organization | Payment method added                                                                             | Organization owner/admin         | Digital self-service |
+| Organization | Personal access key is expiring                                                                  | Account owner                    | All                  |
+| Organization | Machine user access key is expiring                                                              | Organization owner               | All                  |
+| Project      | Upcoming maintenance upgrade on a cluster (24hr)                                                 | Project owner/editor             | All                  |
+| Project      | Successful maintenance upgrade on a cluster                                                      | Project owner/editor             | All                  |
+| Project      | Failed maintenance upgrade on a cluster                                                          | Project owner/editor             | All                  |
+| Project      | Paused cluster will automatically reactivated in 24 hours                                        | Project owner/editor             | All                  |
+| Project      | Paused cluster was automatically reactivated                                                     | Project owner/editor             | All                  |
+| Project      | You must set up the encryption key permission for your CMK-enabled cluster                       | Project owner/editor             | All                  |
+| Project      | Key error with CMK-enabled cluster                                                               | Project owner and project editor | All                  |
+| Project      | User is invited to a project (displays only to the Project owner)                                | Project owner                    | All                  |
+| Project      | New role is assigned to you                                                                      | Account owner                    | All                  |
+| Project      | Role is unassigned from you                                                                      | Account owner                    | All                  |
+| Project      | Failed connection to third-party monitoring integration (and future non-monitoring integrations) | Project owner/editor             | All                  |
+
+!!!note
+All subscription type means Digital self-service, Direct purchase, and Azure Marketplace. For more information, see [subscription types](/biganimal/latest/pricing_and_billing/#payments-and-billing).
+!!!
+
+## Configuring notifications
+
+The project owners/editors and organization owners/admins can configure the notifications for the events visible to them. They can choose if they want to receive notifications in the in-app inbox, email or both. They can also configure email notifications for their teams within their organization. 
+
+Project level notifications are configured within the project.
+
+Notification settings made by a user are applicable only to that user. If an email notification is enabled, the email is sent to the email address associated with the user's login. 
+
+## Viewing notifications
+
+Users in the following roles can view the notifications:
+- Organization owners/admins can view the organization-level notifications. 
+- Project owners/editors can view the project-level notifications.
+- Account owners can view their own account-level notifications. 
+
+Each notification indicates the level and/or project it belongs to for the user having multiple roles within BigAnimal.
+
+Select the bell icon on the top of your BigAnimal portal to view the in-app notifications. On the bell icon, you can read the notification, mark it as unread and also archive the notification.
+
+Check the inbox of your configured email addresses, to view the email notifications.
+
+## Manage notifications
+
+To manage the notifications: 
+1. Log in to the BigAnimal portal.
+1. From the menu under your name in the top right panel, select **My Account**. 
+1. Select the **Notifications tab**. Notifications are grouped by organizations and projects available to you.
+1. Select any specific organization/project to manage the notifications.
+   - Enable/disable the notification for a particular event using the toggle button.
+   - Select the **Email** and **Inbox** next to an event to enable/disable the email and in-app notifications for the event.
+

product_docs/docs/biganimal/release/getting_started/identity_provider/index.mdx

@@ -78,17 +78,60 @@ Once your identity provider is set up, you can view your connection status, ID,
 You need a verified domain so your users can have a streamlined login experience with their email address. 
 
 1. On the **Domains** tab, enter the domain name and select **Next: Verify Domain**. 
-1. Copy the TXT record and follow the instructions. 
-1. Select **Done**. 
+2. Copy the TXT record and follow the instructions in the on screen verify box (repeated below), to add it as a TXT record on that domain within your DNS provider's management console.
 
-   Your domain and its status appear on the **Domains** tab, where you can delete or verify it. Domains can take up to 48 hours to be verified. 
+   - Log in to your domain registrar or web host account.
+   - Navigate to the DNS settings for the domain you want to verify.
+   - Add a TXT record.
+   - In the Name field, enter @.
+   - In the Value field, enter the verification string provided, eg. 
+   - “edb-biganimal-verification=VjpcxtIC57DujkKMtECSwo67FyfCExku”
+   - Save your changes and wait for the DNS propagation period to complete. This can take up to 48 hours.
+
+3. Select **Done**. 
+
+   Your domain and its status appear on the **Domains** tab, where you can delete or verify it. 
+   Domains can take up to 48 hours for the change of the domain record by the DNS provider to propagate before you can verify it. 
+
+4. If your domain has not verified after a day, you can debug whether your domain has the matching verification text field. 
+   Select **Verify** next to the domain at `/settings/domains` to check the exact value of the required TXT field.
+   Query your domain directly with DNS tools, such as nslookup, to check if you have an exact match for a text = "verification" field.
+   Domains can have many TXT fields. As long as one matches, it should verify.
+
+```
+> nslookup -type=TXT mydomain.com
+
+;; Truncated, retrying in TCP mode.
+Server:		192.168.1.1
+Address:	192.168.1.1#53
+Non-authoritative answer:
+...
+mydomain.com	text = “edb-biganimal-verification=VjpcxtIC57DujkKMtECSwo67FyfCExku”
+```
 
 To add another domain, select **Add Domain**. 
 
-When you have at least one verified domain, the identity provider status becomes **Active** on the **Identity Providers** tab. When the domain is no longer verified, the status becomes **Inactive**. 
+When you have at least one verified domain (with Status = Verified, in green), the identity provider status becomes **Active** on the **Identity Providers** tab. 
+When the domain is no longer verified, the status becomes **Inactive**. 
 
 !!! Note
-    The identity provider status can take up to three minutes to update.
+    Your DNS provider can take up to 48 hours to update. Once the domain is verified, the identity provider status can take up to three minutes to update.
+
+### Domain expiry
+
+The EDB system has a 10-day expiry set for checking whether domains are verified.
+
+You buy domains from DNS providers by way of a leasing system. If the lease expires, you no longer own the domain, and it disappears from the Internet.
+If this happens, you need to renew your domain with your DNS provider.
+
+Whether the domain failed to verify within the 10 days or it expired months later,
+it appears as **Status = Expired** (in red).
+You can't reinstate an expired domain
+because expiry means you might no longer own the domain. You need to verify it again.
+
+To delete the domain, select the bin icon.
+To re-create it, select **Add Domain**.
+Set a new verification key for the domain and update the TXT record for it in your DNS provider's management console, as described in [Add a doman](#add-a-domain).
 
 ### Manage roles for added users
 

product_docs/docs/biganimal/release/known_issues/known_issues_dha.mdx → product_docs/docs/biganimal/release/known_issues/known_issues_pgd.mdx

@@ -2,17 +2,22 @@
 title: Known issues with distributed high availability/PGD
 navTitle: Distributed high availability/PGD known issues
 deepToC: true
+redirects:
+- /biganimal/latest/known_issues/known_issues_dha/
 ---
 
-These are currently known issues in EDB Postgres Distributed (PGD) on BigAnimal as deployed in distributed high availability clusters. These known issues are tracked in our ticketing system and are expected to be resolved in a future release. 
+These are currently known issues in EDB Postgres Distributed (PGD) on BigAnimal as deployed in distributed high availability clusters. 
+These known issues are tracked in our ticketing system and are expected to be resolved in a future release. 
 
 ## Management/administration
 
 ### Deleting a PGD data group may not fully reconcile 
-When deleting a PGD data group, the target group resources is physically deleted, but in some cases we have observed that the PGD nodes may not be completely partitioned from the remaining PGD Groups. We recommend avoiding use of this feature until this is fixed and removed from the known issues list.
+When deleting a PGD data group, the target group resources is physically deleted, but in some cases we have observed that the PGD nodes may not be completely partitioned from the remaining PGD Groups. 
+We recommend avoiding use of this feature until this is fixed and removed from the known issues list.
 
 ### Adjusting PGD cluster architecture may not fully reconcile
-In rare cases, we have observed that changing the node architecture of an existing PGD cluster may not complete. If a change hasn't taken effect in 1 hour, reach out to Support. 
+In rare cases, we have observed that changing the node architecture of an existing PGD cluster may not complete. 
+If a change hasn't taken effect in 1 hour, reach out to Support. 
 
 ### PGD cluster may fail to create due to Azure SKU issue
 In some cases, although a regional quota check may have passed initially when the PGD cluster is created, it may fail if an SKU critical for the witness nodes is unavailable across three availability zones.
@@ -28,24 +33,39 @@ If you have already encountered this issue, reach out to Azure support:
 We're going to be provisioning a number of instances of <SKU TYPE> in <TARGET REGION> and need to be able to provision these instances in all AZs. Can you please ensure that subscription <AA BYOA AZURE SUBSCRIPTION> is able to provision this VM type in all AZs of <TARGET REGION>. Thank you!
 ```
 
+### Changing the default database name is not possible
+Currently, the default database for a replicated PGD cluster is `bdrdb`. 
+This cannot be changed, either at initialization or after the cluster is created.
+
 ## Replication
 
 ### A PGD replication slot may fail to transition cleanly from disconnect to catch up 
-As part of fault injection testing with PGD on BigAnimal, you may decide to delete VMs. Your cluster will recover if you do so, as expected. However, if you're testing in a bring-your-own-account (BYOA) deployment, in some cases, as the cluster is recovering, a replication slot may remain disconnected. This will persist for a few hours until the replication slot recovers automatically.  
+As part of fault injection testing with PGD on BigAnimal, you may decide to delete VMs. 
+Your cluster will recover if you do so, as expected. 
+However, if you're testing in a bring-your-own-account (BYOA) deployment, in some cases, as the cluster is recovering, a replication slot may remain disconnected. 
+This will persist for a few hours until the replication slot recovers automatically.  
 
 ### Replication speed is slow during a large data migration
 During a large data migration, when migrating to a PGD cluster, you may experience a replication rate of 20 MBps. 
 
 ### PGD leadership change on healthy cluster
-PGD clusters that are in a healthy state may experience a change in PGD node leadership, potentially resulting in failover. No intervention is needed as a new leader will be appointed.  
+PGD clusters that are in a healthy state may experience a change in PGD node leadership, potentially resulting in failover. 
+No intervention is needed as a new leader will be appointed.  
+
+### Extensions which require alternate roles are not supported
+Where an extension requires a role other than the default role (`streaming_replica`) used for replication, it will fail when attempting to replicate. 
+This is because PGD runs replication writer operations as a `SECURITY_RESTRICTED_OPERATION` to mitigate the risk of privilege escalation.
+Attempts to install such extensions may cause the cluster to fail to operate.
 
 ## Migration
 
 ### Connection interruption disrupts migration via Migration Toolkit 
-When using Migration Toolkit (MTK), if the session is interrupted, the migration errors out. To resolve, you need to restart the migration from the beginning. The recommended path to avoid this is to migrate on a per-table basis when using MTK so that if this issue does occur, you retry the migration with a table rather than the whole database.
+When using Migration Toolkit (MTK), if the session is interrupted, the migration errors out. To resolve, you need to restart the migration from the beginning. 
+The recommended path to avoid this is to migrate on a per-table basis when using MTK so that if this issue does occur, you retry the migration with a table rather than the whole database.
 
 ### Ensure loaderCount is less than 1 in Migration ToolKit 
-When using Migration Toolkit to migrate a PGD cluster, if you adjusted the loaderCount to be greater than 1 to speed up migration, you may see an error in the MTK CLI that says “pgsql_tmp/': No such file or directory.” If you see this, reduce your loaderCount to 1 in MTK. 
+When using Migration Toolkit to migrate a PGD cluster, if you adjusted the loaderCount to be greater than 1 to speed up migration, you may see an error in the MTK CLI that says “pgsql_tmp/': No such file or directory.” 
+If you see this, reduce your loaderCount to 1 in MTK. 
 
 ## Tools
 

product_docs/docs/biganimal/release/release_notes/index.mdx

@@ -2,6 +2,7 @@
 title: BigAnimal release notes
 navTitle: Release notes
 navigation:
+- mar_2024_rel_notes
 - feb_2024_rel_notes
 - jan_2024_rel_notes
 - dec_2023_rel_notes
@@ -22,6 +23,7 @@ The BigAnimal documentation describes the latest version of BigAnimal, including
 
 | Month                                |
 |--------------------------------------|
+| [March 2024](mar_2024_rel_notes)     |
 | [February 2024](feb_2024_rel_notes)  |
 | [January 2024](jan_2024_rel_notes)   |
 | [December 2023](dec_2023_rel_notes)  |

product_docs/docs/biganimal/release/release_notes/mar_2024_rel_notes.mdx

@@ -0,0 +1,15 @@
+---
+title: BigAnimal March 2024 release notes
+navTitle: March 2024
+---
+
+BigAnimal's March 2024 includes the following enhancements and bugfixes:
+
+| Type | Description |
+|------|-------------|
+| Enhancement | EDB Postgres Extended Server is now available in BigAnimal for single-node, high-availability, and Distributed High Availability clusters. |
+| Enhancement | You can now use Transparent Data Encryption (TDE) for clusters running on EDB Postgres Advanced Server or EDB Postgres Extended Server versions 15 and later in BigAnimal’s AWS account. With TDE, you can connect your keys from AWS’s Key Management Service to encrypt your clusters at the database level in addition to the default volume-level encryption. |
+| Enhancement | BigAnimal Terraform provider v0.8.1 is now available. Learn more about what’s new [here](https://github.com/EnterpriseDB/terraform-provider-biganimal/releases/tag/v0.8.1) and download the provider [here](https://registry.terraform.io/providers/EnterpriseDB/biganimal/latest). |
+| Enhancement | BigAnimal CLI v3.6.0 is now available. Learn more about what’s new [here](https://cli.biganimal.com/versions/v3.6.0/). |
+
+