Skip to content

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jul 28, 2025

Backport of #10700 to release/9.4

/cc @mitchdenny @copilot

Customer Impact

We found a bug related to using the aspire run and aspire 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?

Copilot AI and others added 2 commits July 28, 2025 15:13
Co-authored-by: mitchdenny <513398+mitchdenny@users.noreply.github.com>
@mitchdenny mitchdenny self-assigned this Jul 28, 2025
@mitchdenny mitchdenny requested a review from joperezr July 28, 2025 15:21
@mitchdenny mitchdenny added this to the 9.4 milestone Jul 28, 2025
@mitchdenny mitchdenny changed the title [release/9.4] [WIP] aspire config set writes appHostPath to ~/.aspire/settings.json globally, causing incorrect path resolution [release/9.4] aspire config set writes appHostPath to ~/.aspire/settings.json globally, causing incorrect path resolution Jul 28, 2025
@eerhardt
Copy link
Member

Should we even be writing the appHostPath to the global settings file at all? That seems like a more core issue than the name of the file.

@davidfowl
Copy link
Member

9.4.1

@davidfowl
Copy link
Member

@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?

@mitchdenny
Copy link
Member

Yes this is the right fix.

@mitchdenny
Copy link
Member

Should we even be writing the appHostPath to the global settings file at all? That seems like a more core issue than the name of the file.

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 ;)

@davidfowl davidfowl modified the milestones: 9.4, 9.4.1 Jul 30, 2025
@davidfowl
Copy link
Member

I put this in 9.4.1 @joperezr

@joperezr joperezr added the Servicing-approved Approved for servicing release label Aug 1, 2025
@joperezr joperezr merged commit 825b309 into release/9.4 Aug 1, 2025
502 of 504 checks passed
@joperezr joperezr deleted the backport/pr-10700-to-release/9.4 branch August 1, 2025 22:08
@dotnet-policy-service dotnet-policy-service bot modified the milestone: 9.4.1 Aug 1, 2025
WeihanLi pushed a commit to WeihanLi/aspire that referenced this pull request Aug 13, 2025
…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>
This was referenced Aug 27, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Sep 1, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants