Include PG Replication User Option

[bhardwajRahul]

This PR aims at updating documentation for Add a Database User

• This API call will create a postgres cluster user with replication rights i.e. pg_allow_replication.

• Sample curl request and response.

Request

curl -X POST \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $DIGITALOCEAN_TOKEN" \
  -d '{"name": "app-01", "settings":{"pg_allow_replication":true}}' \
  "https://api.digitalocean.com/v2/databases/9cc10173-e9ea-4176-9dbc-a4cee4c4ff30/users"
  

Response

{
  "user": {
    "name": "app-01",
    "role": "normal",
    "password": "jge5lfxtzhx42iff"
    "settings": {
       "pg_allow_replication":true
       }
    }
}

[gitguardian]

⚠️ GitGuardian has uncovered 5 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-		Generic Password	ae7a0e8	specification/resources/databases/responses/user.yml	View secret
-		Generic Password	2e5c072	specification/resources/databases/responses/user.yml	View secret
-		Generic Password	2e5c072	specification/resources/databases/responses/user.yml	View secret
-		Generic Private Key	ae7a0e8	specification/resources/databases/models/database_user.yml	View secret
-		Generic Private Key	2e5c072	specification/resources/databases/models/database_user.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[andrewsomething]

Setting this to requiring changes to prevent it accidentally being merged as per the discussion in Slack.

[andrewsomething]

👍 LGTM!