Implement interim solution for secrets management
As an EDS Developer, I want my code to securely store and retrieve secrets so that the Fetch and Ingest DAGs can connect to external sources.
- A Secret Service API is coming in a later sprint. In the "interim", the DAG code will need to directly interact with the secret manager. This could be by directly calling the secret manager's APIs or using a resource-specific library or SDK that interacts with it. This code will later be refactored to use the APIs. See the linked issue on this ticket for more information.
- EDS Developers understand how to use the secret manager resource
- Fetch and Ingest DAG code is retrieving secrets from the secret manager by the key that is in the ConnectedSourceRegistryEntry
- The code has unit tests
- The code has been merged to master