The default PowerShell profile is not properly handled.
kherrera-ebsco opened this issue · comments
The following checks have been done.
- I could not find another bug report that covers what I discovered.
- This report does not request new features or enhancements.
What is the current behavior?
The application does not integrate into the correct PowerShell profile.
What is the expected behavior?
The application properly detects the active PowerShell profile and uses it for integration.
Some additional context.
- The application assumes that the profile is always in one location, which is not necessarily the case.
- A StackOverflow provided a nice explanation on how PowerShell profiles can be discovered.
It would be nice to also warn the user during the PowerShell integration process that the aws-login shell install command may need to be executed for other profiles they may be using.