Transition from a regular PostgreSQL connector to PostgreSQL SSH connector
We want to start using the "PostgreSQL SSH" connector in place of the regular one. We already have a number of datasets created, so I'm wondering if there's an easy way to have a dataset use the new SSH connector. I really want to avoid recreating all of the datasets.
The post below makes it sound like this isn't possible in an easy way, but it's a few years old. My hope is that there's a better answer to this issue.
Thanks in advance!
Comments
-
I think you're out of luck still on this one. Switching connector types requires a different type of credential / integration account and changing that in a dataset isn't really an accessible method. You could see if Support has any backend tricks to help accommodate...if you find out please let us know.
In the meantime if you go for a manual migration, just come up with a plan after doing an impact review using stats/governance datasets to get a checklist down. If any of those datasets to migrate have cards pointing directly at them or beast modes on them, it would be a good time to put in a prep layer transform and clean up any beasts too.
1
Categories
- All Categories
- 1.4K Product Ideas
- 1.4K Ideas Exchange
- 1.4K Connect
- 1.1K Connectors
- 282 Workbench
- 3 Cloud Amplifier
- 4 Federated
- 2.8K Transform
- 86 SQL DataFlows
- 548 Datasets
- 2.2K Magic ETL
- 3.2K Visualize
- 2.3K Charting
- 543 Beast Mode
- App Studio
- 26 Variables
- 566 Automate
- 134 Apps
- 411 APIs & Domo Developer
- 21 Workflows
- DomoAI
- 28 Predict
- 12 Jupyter Workspaces
- 16 R & Python Tiles
- 344 Distribute
- 86 Domo Everywhere
- 257 Scheduled Reports
- 1 Software Integrations
- 85 Manage
- 84 Governance & Security
- 6 Product Release Questions
- Community Forums
- 41 Getting Started
- 27 Community Member Introductions
- 81 Community Announcements
- 4.8K Archive