-
Notifications
You must be signed in to change notification settings - Fork 0
[Data Sync] Handle database credentials #47
Comments
Handling Jenkins to access Vault to handle credentials. |
rolled over from sprint 23 |
This issue is blocked by bcgov/nr-spar-data-sync#26 and bcgov/nr-spar-data-sync#27 issues, regarding the change of Jenkins Server from Cron to Polaris. |
rolled over from Sprint 24 |
This issue is blocked by bcgov/nr-spar-data-sync#30 (Vault credentials gathering implementation in Jenkins Polaris). |
rolled over from sprint 25 to 26 |
…s to connect into OC
Updates for this task, so far: I finally could use the Openshift Client inside a Podman instance (at least to run "oc version" command). I tried:
|
Latest error: STEP 22/25: RUN ./oc_bin/oc login --token=$oct --server=$ocs Requesting help to 1Team. |
This issue will need to be rolled up to the next sprint. |
Rolled over from sprint 23 |
This issue should be closed, as the old repo does not exists anymore (new repo is nr-spar-data). |
Obtain database connection in Oracle Database and Postgres Database using safe stored credentials obtained by a Secret Engine.
Background: Data Sync Engine Needs to obtain connection in databases in run time execution. Credentials must be obtained during runtime in requests to a secrets management engine.
Acceptance Criteria:
The text was updated successfully, but these errors were encountered: