Describe the bug
After I run az aks use-dev-spaces -g RGName -n Name, the .bash_profile is created.
source /etc/bash_completion.d/azds
These are two common files .profile and .bash_profile in bash environment, but only one file will be applied. The .bash_profile is first priority. But in WSL, only .profile exists by default.
For example, in my box, I don't have a .bash_profile by default. All my profile settings are write in .profile file. After run az aks user-dev-spaces command, the .bash_profile been created. After I re-open WSL again, the .profile file is ignored because there is a .bash_profile file exist.
To Reproduceaz aks use-dev-spaces -g RGName -n Name under WSL.
Expected behavior
If there is a .profile file, use this one. If there is already has a .bash_profile, then use .bash_profile.
Environment summary
Bash on Windows
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
Describe the bug After I run
az aks use-dev-spaces -g RGName -n Name
, the.bash_profile
is created.These are two common files
.profile
and.bash_profile
in bash environment, but only one file will be applied. The.bash_profile
is first priority. But in WSL, only.profile
exists by default.For example, in my box, I don't have a
.bash_profile
by default. All my profile settings are write in.profile
file. After runaz aks user-dev-spaces
command, the.bash_profile
been created. After I re-open WSL again, the.profile
file is ignored because there is a.bash_profile
file exist.To Reproduce
az aks use-dev-spaces -g RGName -n Name
under WSL.Expected behavior If there is a
.profile
file, use this one. If there is already has a.bash_profile
, then use.bash_profile
.Environment summary
Bash on Windows
Additional context