ipfs/kubo

--config not respected during migration

Open

#3,076 opened on Aug 12, 2016

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (13,906 stars) (2,725 forks)batch import
help wantedkind/bugstatus/deferred

Description

Version/Platform/Processor information (from ipfs version --all): go-ipfs version: 0.4.3-rc3- Repo version: 4 (--config also not respected by ipfs version --all) System version: amd64/linux Golang version: go1.6.2

Type (bug, feature, meta, test failure, question): bug Area (api, commands, daemon, fuse, etc): commands Priority (from P0: functioning, to P4: operations on fire): P1

Description: I can't migrate my nonstandard repo location. --config is ignored. ipfs keeps migrating ~/.ipfs instead of the path I pass in. It seems the parameter is not passed on to the migration binary.

Contributor guide

Tech stack
go
Domain
backendcli
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Gocommand line flagsIPFS migration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate how the config flag is passed to the migration subcommand. Start by examining the command line parsing in the main entry point (e.g., cmd/ipfs/main.go) and trace the config path through migration initialization. Look at related commands like 'ipfs init' which may correctly handle config for reference. Check if there is a struct or function that holds config options and whether it is populated before migration runs.