DBaaS: Add API endpoint for applying cluster patches

[vsharma6855]

No description provided.

[andrewsomething]

Looks great, but I did have a suggestion in-line re: operationId

[andrewsomething]

The operation ID is used by client generation tools to produce the method name. For example pydo, our Python client, will end up having a method with the redundant name databases.update_install_update. This might be more natural:

Suggested change

	operationId: databases_update_installUpdate
	operationId: databases_install_update

Our linter enforces using consistent operation IDs across our API. As this would be the first PUT using install, you'll also need to add it here so that it passes:

openapi/spectral/functions/validateOpIDNaming.js

Line 14 in 6fddf79

const PUT = ["update", "promote"];

[andrewsomething]

I've pushed an additional commit to allow this to pass the linter check: e41ef07

[loosla]

I believe a single line in between should be enough.

[loosla]

Looks good to me

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret 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.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
13808615	Triggered	Basic Auth String	11eb0dc	specification/resources/databases/models/opensearch_connection.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.

---

^{🦉 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.}