ipfs-cluster/cmd/ipfs-cluster-service
Kishan Sagathiya b96c2b664d Do not load API components removed from the config (#836)
* Do not load API components removed from the config

This commit introduces a map that would keep track of whether components
for a component were missing or not from the JSON config file. This map
can be check while creating cluster to avoid loading a component.

It would consider component only if the component is fully missing from the
config.
Say the component in question is `ipfsproxy` which is under `api`
section.
This would use defaults for `ipfsproxy` and load IPFS proxy.

```
{
"api":{
	"ipfsproxy": {}
	}
}
```

However, this would not load IPFS proxy
```
{
"api":{}
}
```
2019-07-18 17:33:14 +02:00
..
dist Move ipfs-cluster-service and ipfs-cluster-ctl to cmd/ 2018-09-27 20:56:09 +02:00
configs.go service: multiple fixes around init and identities 2019-05-16 15:31:36 +02:00
daemon.go Do not load API components removed from the config (#836) 2019-07-18 17:33:14 +02:00
lock.go service: multiple fixes around init and identities 2019-05-16 15:31:36 +02:00
main.go service: multiple fixes around init and identities 2019-05-16 15:31:36 +02:00
Makefile Move ipfs-cluster-service and ipfs-cluster-ctl to cmd/ 2018-09-27 20:56:09 +02:00
state.go Fix #787: Connectivity fixes 2019-05-27 14:27:23 +02:00