Tried changing the port of the existing localhost postgres database connection to use the remote OC dev postgres database, but then all the table mapping gets mismatched for some reason.
Created an new ETL task, "PIMS ETL Prod to Dev" for running against Dev, Test, and Prod Openshift environments because it doesn't seem that DBeaver allows you to use the same database task against multiple databases.
I also, included a "data-sources.json" file which should include the connection string that the new ETL task uses, you probably will need to enter the db name, username and password, port number should be 127.0.0.1:22224.
I also removed 2 older ETL tasks that were outdated, so you should now only see these 2 tasks, one for running locally and the other one for running against the Openshift environments.
🔰 Checklist
[x] I have read and agree with the following checklist and am following the guidelines in our Code of Conduct document.
I have performed a self-review of my code.
I have commented my code, particularly in hard-to-understand areas.
I have made corresponding changes to the documentation where required.
I have tested my changes to the best of my ability.
Tried changing the port of the existing localhost postgres database connection to use the remote OC dev postgres database, but then all the table mapping gets mismatched for some reason.
Created an new ETL task, "PIMS ETL Prod to Dev" for running against Dev, Test, and Prod Openshift environments because it doesn't seem that DBeaver allows you to use the same database task against multiple databases.
I also, included a "data-sources.json" file which should include the connection string that the new ETL task uses, you probably will need to enter the db name, username and password, port number should be 127.0.0.1:22224.
I also removed 2 older ETL tasks that were outdated, so you should now only see these 2 tasks, one for running locally and the other one for running against the Openshift environments.
🔰 Checklist