MonkeyCanCode commented on PR #4770: URL: https://github.com/apache/polaris/pull/4770#issuecomment-4725677126
> One difference I was thinking about is the user workflow. > > With AWS, credentials are something many users interact with regularly across multiple accounts, profiles, and tools, so matching established AWS CLI conventions has a lot of value. > > > > For Polaris, my impression is that the client secret is usually entered once when a profile is created and then rarely revisited. In that workflow, hiding the secret during entry feels a bit more natural since users are typically copy/pasting a generated value rather than typing and managing credentials day to day. > > > > Curious to hear both your thoughts on that perspective, @MonkeyCanCode and @dimas-b. > > IMO, it should be similar. Take an example, assuming I have 3 AWS accounts (dev, qa, and prod), I would create 3 profiles and one for each. Then when using AWS CLI, I would use '--profile xxx' depends on which env I am working with. In this case, I would need to create 3 profiles (which CLI will show plain text when setting up profiles). Now assuming we do the same for Polaris root account per AWS env, I would expected to perform the same setup profile 3 times (one per env). In this case, the profile is only created once per environment. This can be handy imo when we are creating new principal where a random client id and client secret will be print to screen. In this case, I would think it is cleaner to show plain text when setting up profile for this new principal (as I not 100% sure what I have in my clipboard...I could paste to another terminal to verify but extra step IMO). -- 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]
