Value Statement

ARC-HCP requires to support entra auth for postgres by maestro

Definition of Done for Engineering Story Owner (Checklist)

• introduce --db-auth-method as a parameter of maestro. the available value is az-entra/postgres. if set as postgres, use regular password to authenticate. if set as az-entra, use access token to authenticate.
• use --db-password-file to pass the regular password. for az-entra, this parameter can be ignore. we need to call azure sdk to get the access token. the datastore_uri likes postgresql://postgres:${access_token}@postgres_cluster. we can refer to this PR - https://gitlab.cee.redhat.com/service/uhc-clusters-service/-/merge_requests/8779/diffs 

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.