The Lyftron Provider for DigitalOcean offers the most natural way to access DigitalOcean data from Lyftron with ease and also enables to connect with BI, MDM & ML tools, Data warehouses, Databases and other SAAS based applications with zero code and zero infrastructure requirements. The provider wraps the complexity of accessing DigitalOcean data into easy-to-integrate relational fully managed ANSI Sql format. Make faster and better business decisions with Lyftron’s DigitalOcean data provider and automatically build your data migration pipelines in minutes, not months
The provider hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.
- Comprehensive Delta load mechanism.
- Real-time access to DigitalOcean.
- Comprehensive full support of ANSI Sql to query data with ease.
- Collaborative query processing.
The user must have credentials for DigitalOcean, Lyftron and your destination data warehouse, lake or database to perform the data pipeline operation with Lyftron
Establishing a Connection with Lyftron's Quickstart Steps
Create your DigitalOcean connection with Lyftron by following the 5 easy steps show below:
Step1. Add your connection
Click on Connect section on the left panel → Click on Add Connection button
Step2. Select your connector
In the connector selection panel, search and click DigitalOcean for your connection
Step3. Enter your connection details
In the Connection String section enter the values of the below parameters. The following connection string is required to establish DigitalOcean connection with Lyftron."InitiateOAuth=GETANDREFRESH;OAuthClientId=MyOAuthClientId;OAuthClientSecret=MyOAuthClientSecret;CallbackURL=http://localhost:portNumber"
|Connection Name||Enter your connection details||Required|
|OAuthClientId||Your DigitalOcean OAuthClientId||Required|
|OAuthClientSecret||Your DigitalOcean OAuthClientSecret||Required|
|Logfile**||Use the logfile option to debug your job and provide your connection name to generate the log file. [ConnectionConfigurationPath]\Connection_name_log.tx||Optional|
|Verbosity**||Choose verbosity 1-5 based on the severity of debugging||Optional|
** For more information, check the Lyftron logging and debugging section.
If you want more detailed information about how to establish a connection with Lyftron, click on Lyftron Connection Quick Start guide.
Step4. Test your connection
Once you are done entering your connection details, simply click on the Test Connection button to test the connectivity. In case your connection fails, add Logfile and Verbosity parameters and check the Lyftron logging and debugging section, to debug the error.
Step5. Save your connection
The Lyftron Provider for DigitalOcean models entities in the DigitalOcean API as tables, view. These are defined in schema files, which are simple, text-based configuration files.
Using Collaborative Query Processing
The provider offloads as much of the SELECT statement processing as possible to the DigitalOcean APIs and then processes the rest of the query within the provider. The following sections document API limitations and requirements. See SupportEnhancedSQL for more information on how the provider circumvents API limitations with in-memory client-side processing.
Views are tables that cannot be modified. Typically, read-only data are shown as views
Views are composed of columns and pseudo columns. Views are similar to tables in the way that data is represented; however, views do not support updates. Entities that are represented as views are typically read-only entities. Often, a stored procedure is available to update the data if such functionality is applicable to the data source.
Queries can be executed against a view as if it were a normal table, and the data that comes back is similar in that regard.
|Account||Views||Retrieves user information in DigitalOcean.|
|Actions||Views||Retrieve Actions in DigitalOcean.|
|Backups||Views||Retrieve volume backups in DigitalOcean.|
|Certificates||Views||Retrieve SSL Certificates in DigitalOcean.|
|DatabaseClusters||Views||Retrieve information regarding the database clusters.|
|DatabaseConnectionPools||Views||Retrieve information regarding PostgreSQL database connection pools.|
|DatabaseFirewallRules||Views||Retrieve information regarding the database firewall rules.|
|DatabaseReplicas||Views||Retrieve information regarding the database replicas. Read-only replicas are not supported for Redis clusters.|
|DomainRecords||Views||Retrieve Domain Records in DigitalOcean.|
|Domains||Views||Retrieve Domains in DigitalOcean.|
|Droplets||Views||Retrieve Droplets in DigitalOcean.|
|DropletsNetworks||Views||Retrieve Networks configured for Droplets in DigitalOcean.|
|Firewalls||Views||Retrieve Firewalls in DigitalOcean.|
|FirewallsInBoundRules||Views||Retrieve Inbound rules for Firewalls in DigitalOcean.|
|FirewallsOutBoundRules||Views||Retrieve Outbound rules for Firewalls in DigitalOcean.|
|FirewallsPendingChanges||Views||Retrieve Pending Changes for Firewalls in DigitalOcean.|
|FloatingIPs||Views||Retrieve Floating IPs in DigitalOcean.|
|Images||Views||Retrieve images in DigitalOcean.|
|Kernels||Views||Query Kernels available to a Droplet in DigitalOcean.|
|LoadBalancers||Views||Retrieve Load Balancers in DigitalOcean.|
|LoadBalancersForwardingRules||Views||Retrieve Forwarding rules for Load Balancers in DigitalOcean.|
|Regions||Views||Retrieve Regions in DigitalOcean.|
|Sizes||Views||Retrieve all of the Sizes in DigitalOcean.|
|Snapshots||Views||Retrieve droplet or volume snapshots in DigitalOcean.|
|SSHKeys||Views||Retrieve SSH Keys in DigitalOcean.|
|Tags||Views||Retrieve tags in DigitalOcean.|
|Volumes||Views||Retrieve volumes in DigitalOcean.|