MonkeyCanCode commented on PR #1474: URL: https://github.com/apache/polaris/pull/1474#issuecomment-2836764827
Got it. Thanks for confirmation. Yes, if the tool will support export/import, then yes. In this case, an end-user can prep the input file for refresh env as well. Alright, let me know how it goes and I should add more code to this PR. > > So the sync tool is mainly for migration purpose I think where a end-user will need to have the setup first to be able to use that. > > Conceptually I agree. However [something that came up](https://lists.apache.org/thread/5p96vdvj5x68kfhk8f8vxo51v0y5x769) during design/review of the sync tool is exactly this. Dump one Polaris to a file, then apply that file to another Polaris. If implemented, that seems identical to the functionality we'd have here for `setup`s. So we should probably figure out which direction we want to go with this. > > > For example, assuming I have dev, stage, and prod and I want the basic entities ... to be the same > > You could do this with the sync tool right? Also, with both the setup and the sync tool, the Principal credentials would potentially be different. And in the case of the setup as it's currently implemented, how do you even get the principal secrets in a structured way? > > > The one thing I am debating myself is support update/delete operations. > > The sync tool has the concept of different [modes](https://github.com/apache/polaris-tools/commit/46fe5e057e617eecee4da41bc36791736e3c55de) -- 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]
