Issue: Database credentials needs to be handled by a secrets engine (Vault) to be injected in the Source Code of Data Sync Engine in Run Time execution, avoiding data leakage.
Background: Vault access was configured in Jenkins Cron server, but needs to be implemented in the Jenkins Polaris architecture, using podman containerized application.
1: Sample Dummy code retrieving data from Vault and checking if K/V are expected.
2: Documentation in Confluence Page.
Ticket Reference
This ticked blocks Issue bcgov/nr-spar-data#47 as database credentials are stored in Vault, so first is needed to implement a vault access to Jenkins Polaris execution instance.
Issue: Database credentials needs to be handled by a secrets engine (Vault) to be injected in the Source Code of Data Sync Engine in Run Time execution, avoiding data leakage.
Background: Vault access was configured in Jenkins Cron server, but needs to be implemented in the Jenkins Polaris architecture, using podman containerized application.
List of base documentation to implement:
Acceptance Criteria:
1: Sample Dummy code retrieving data from Vault and checking if K/V are expected. 2: Documentation in Confluence Page.
Ticket Reference
This ticked blocks Issue bcgov/nr-spar-data#47 as database credentials are stored in Vault, so first is needed to implement a vault access to Jenkins Polaris execution instance.