Add secret file format for object storage

Signed-off-by: Shruti Deshpande <shdeshpa@redhat.com>

Author: shdeshpa07

modules/oadp-creating-default-secret.adoc

@@ -30,15 +30,43 @@ If you do not want to use the backup location credentials during the installatio
 
 * Your object storage and cloud storage, if any, must use the same credentials.
 * You must configure object storage for Velero.
-* You must create a `credentials-velero` file for the object storage in the appropriate format.
 
 .Procedure
 
-* Create a `Secret` with the default name:
+. Create a `credentials-velero` file for the backup storage location in the appropriate format for your cloud provider.
+
+ifdef::installing-oadp-aws,installing-oadp-mcg,installing-oadp-ocs[]
++
+See the following example:
++
+[source,terminal]
+----
+[default]
+aws_access_key_id=<AWS_ACCESS_KEY_ID>
+aws_secret_access_key=<AWS_SECRET_ACCESS_KEY>
+----
+endif::[]
+ifdef::installing-oadp-azure[]
++
+See the following example:
++
+[source,terminal]
+----
+AZURE_SUBSCRIPTION_ID= <azure_subscription_id>
+AZURE_TENANT_ID=<azure_tenant_id>
+AZURE_CLIENT_ID=<azure_client_id>
+AZURE_CLIENT_SECRET=<azure_client_secret>
+AZURE_STORAGE_ACCOUNT_ACCESS_KEY=<azure_storage_account_access_key>
+AZURE_RESOURCE_GROUP=<azure_resource_group>
+AZURE_CLOUD_NAME=<azure_cloud_name>
+----
+endif::[]
+
+. Create a `Secret` custom resource (CR) with the default name:
 +
 [source,terminal,subs="attributes+"]
 ----
 $ oc create secret generic {credentials} -n openshift-adp --from-file cloud=credentials-velero
 ----
 
-The `Secret` is referenced in the `spec.backupLocations.credential` block of the `DataProtectionApplication` CR when you install the Data Protection Application.
+The `Secret` is referenced in the `spec.backupLocations.credential` block of the `DataProtectionApplication` CR when you install the Data Protection Application.