fivetran-arunsuri commented on issue #1929: URL: https://github.com/apache/polaris/issues/1929#issuecomment-3044226999
Thanks for the response, @dimas-b. Using the Admin Tool for principal manipulation would introduce additional complexity to our migration workflow. Our primary requirement is to retain the same client credentials (clientId and clientSecret) across both versions of Polaris (0.9 and 1.0), ensuring a smooth migration path and the ability to roll back seamlessly in case of unforeseen issues. Introducing support for optional clientId and clientSecret parameters in the createPrincipal API request body appears to be the most straightforward and practical solution for our use case. It would eliminate the need for manual credential injection or tool-based workarounds and provide a consistent way to maintain credential continuity during version transitions. Additionally, we believe this capability could be beneficial to others who are migrating between versions of Polaris and want to preserve existing user credentials without disruption. It would be great to get your thoughts on this direction. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
