Move all configuration to the global config dir #2079
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fnando
force-pushed
the
global-config-dir
branch
from
92854ce to
6912b5d
Compare
fnando
force-pushed
the
global-config-dir
branch
from
6912b5d to
bfcb357
Compare
fnando
changed the title
|
💯 So awesome we're doing this now. As a user reading the output messages indicating that there's a local config present that needs migrating, I'd benefit from understanding what's in the local config. If it's too difficult to identify what's in the config, maybe:
|
|
@leighmcculloch ended up going with this: $ stellar keys address me
⚠️ A local config was found at ".stellar".
This behavior is deprecated and will be removed in the future.
Run `stellar config migrate` to move the configuration to "/Users/fnando/.config/stellar". |
leighmcculloch
approved these changes
Jul 18, 2025
leighmcculloch
approved these changes
Jul 18, 2025
leighmcculloch
approved these changes
Jul 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Add change that will deprecate local config directories in p23. This also adds a config migration command
stellar config migratethat moves over configs from local to globalWrite operations (create/delete) are only done in global dir, while read operations (e.g. fetch alias) use both local (have priority, like in older versions) and global.
If local gets hit, it will print a warning.
Examples of running commands:
v23:
No warning when using alice-global
User can migrate their configurations using
stellar config migratecommand. (This command takes care of all configs at once, but we might change it in the future)This command will be available past protocol-23
Given local:
And global:
We can run migration:
As the result, local config will be deleted and global will look like:
All duplicated files have prefix (unique to original path) to avoid accidental overriding when migrating multiple local configs (e.g. if there are multiple alice keys, one per project) -- user can rename those files later based.
Running it again will simply print that no migration is needed
In addition,
--config-dirallows to change config directory from global:Finally, passing
--globalflag emits warning:Why
#1993
Known limitations
Warnings can not be muted with -q flag
Sometimes warnings are printed multiple times (e.g. contract deploy)