Skip to main content

Community

Destination Improvement: add Rest API endpoint to generate client id and secret for the Managed Datalake Polaris server

Completed

Please sign in to leave a comment.

Comments

3 comments

  • Official comment
    Hi Rui Yang,

    Thank you so much for submitting this feature request! Enabling a REST API endpoint to generate client ID and secret for the Managed Datalake Polaris server is a valuable idea, and I appreciate you taking the time to share it with us.

    I’ve added your request to our feature improvements backlog for consideration by our product team.

    We value your input and will keep the community updated in this thread as we make progress. Thank you again for helping us improve Fivetran!

    Best regards,
    Casey Karst
    Hi Rui Yang,

    Thank you so much for submitting this feature request and sharing your idea! Adding a REST API endpoint to generate client IDs and secrets for the Managed Datalake Polaris server is a valuable suggestion, and I can see how it could help streamline integrations and automation.

    I've added your request to our feature improvements backlog for further review.

    We'll keep this thread updated with any developments or progress. Thank you again for helping us make Fivetran better!

    Best regards,
    Casey Karst

    Hi Rui, 
    I wanted to reach out and tell you that improvements have been made to our REST API. 
    Specifically when you create a destination of type managed_data_lake we will return the polaris_catalog_configuration. This will enable your workload!

    Thanks for the great feature request. 

    https://fivetran.com/docs/rest-api/api-reference/destinations/create-destination?service=managed_data_lake#polaris_catalog_configuration