-
Notifications
You must be signed in to change notification settings - Fork 686
[release/9.4] aspire config set writes appHostPath to ~/.aspire/settings.json globally, causing incorrect path resolution #10703
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: mitchdenny <513398+mitchdenny@users.noreply.github.com>
Should we even be writing the |
9.4.1 |
@mitchdenny we should take this PR for 9.4.1 for sure, once youre in this state it always happens.. We have more time now so is this the fix we want? |
Yes this is the right fix. |
We didn't write it to the global file. We wrote it to a local file that just happened to occupy the same space as the global file ;) |
I put this in 9.4.1 @joperezr |
…ngs.json globally, causing incorrect path resolution (dotnet#10703) * Initial plan * Rename global settings file from settings.json to globalsettings.json Co-authored-by: mitchdenny <513398+mitchdenny@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: mitchdenny <513398+mitchdenny@users.noreply.github.com>
Backport of #10700 to release/9.4
/cc @mitchdenny @copilot
Customer Impact
We found a bug related to using the
aspire run
andaspire config
commands when there is a global aspire configuration file in$HOME/.aspire/settings.json
. Basically because the local config is.aspire/settings.json
and we search up the directory tree, it will find the global config and put settings in that.To solve this problem we renamed the global configuration file to
.aspire/globalsettings.json
to avoid this conflict.Testing
Automated tests already used this approach for test isolation. Also did manual testing.
Risk
Low.
Regression?