[YAML][Feature Request]: Integration and Usage of GCP Secret Manager with the different Apache Beam IOs

[eder001]

What would you like to happen?

I would like to use GCP Secrete manager to avoid passing user/password information as a parameter inside the YAML file

Issue Priority

Priority: 2 (default / most feature requests should be filed as P2)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam YAML
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Infrastructure
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner

[ffernandez92]

I think this makes sense. I'd assume the main pain point at this stage is JDBC, but I could be wrong. I remember discussing this same issue during the last Beam Summit [@Polber , @robertwb]. Jinja templates address this problem at the YAML level; however, once in the Dataflow UI, the data is displayed as plain text. Ideally, I would make this more generic to also support AWS Secret Manager (or secret managers in general) using some sort of factory pattern to handle different types. I'm happy to open a discussion and even contribute to the implementation if needed.

[eder001]

@ffernandez92 @robertwb any update?

[liferoad]

https://docs.google.com/document/d/1Ng00Kw-vnG9kKd3RteC6Q5_YN8yDtXRDHkn570GPQrY/edit?tab=t.0#heading=h.c0uts5ftkk58 has some discussion.

[github-actions]

This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.

[damccorm]

Not stale - I think we still want to do this, it just has not been prioritized yet