Adding missed out config in Docs (#7493)

* Adding missed out config in Docs

Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com>

* Removing format

Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com>

Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com>

components/docs-chef-io/content/automate/ha_onprim_deployment_procedure.md

@@ -103,8 +103,10 @@ sudo sed -i 's/SELINUX=enforcing/SELINUX=permissive/g' /etc/selinux/config
    - Give the `ssh_key_file` path; this key should have access to all the Machines or VMs.
    - `sudo_password` is only meant to switch to sudo user. If you have configured a password for the sudo user, please provide it here.
    - We support only private key authentication.
-   - Give `fqdn` as the DNS entry of Chef Automate, which LoadBalancer redirects to Chef Automate Machines or VMs. Example: `chefautomate.example.com`
-   - Set the `admin_password` to what you want to use to log in to Chef Automate when you open up `chefautomate.example.com` in the Browser, for the username `admin`.
+   - Provide `backup_config` based on the type of backup storage you have. This field can be optionally left empty during deployment and can be patched at later point. Allowed values are `object_storage` and `file_system`.
+   - If `backup_config` is `object_storage`, make sure to fill values under `[object_storage.config]`
+   - Give `fqdn` as the DNS entry of Chef Automate, which LoadBalancer redirects to Chef Automate Machines or VM's. Example: `chefautomate.example.com`
+   - Set the `admin_password` to what you want to use to login to Chef Automate, when you open up `chefautomate.example.com` in the Browser, for the username `admin`.
 
    {{< note >}} Click [here](/automate/ha_cert_deployment) to learn more about adding certificates for services during deployment. {{< /note >}}
 
@@ -128,7 +130,10 @@ sudo sed -i 's/SELINUX=enforcing/SELINUX=permissive/g' /etc/selinux/config
 ### Sample config
 
 {{< note >}}
-Assuming 10+1 nodes (1 bastion, 2 for automate UI, 2 for Chef-server, 3 for Postgresql, 3 for OpenSearch)
+
+- Assuming 10+1 nodes (1 bastion, 2 for automate UI, 2 for Chef-server, 3 for Postgresql, 3 for Opensearch)
+- Following config will by default leave the backup configuration empty
+
 {{< /note >}}
 
 ```config