Refactor EDS DAGs to use Secret Service
As an EDS Solution Architect I want the EDS core fetch and ingest DAGS to utilize a common interface for secret management so that so that CSP implementation is not tightly coupled to the EDS DAGs.
Acceptance Criteria
- EDS DAGs that add or retrieve secrets are using the Secret Service or Python SDK incorporating the Secret Service
- Refactored code is covered by test cases
- Code is merged into master
- Code is deployed to development environment
Tasks
- Understand the Secret Service and/or SDK
- Refactor code to remove temporary workaround implementation
- Unit test code
- Create a merge request
- Ensure merged code is deployed to development environment