ipfs-cluster/config
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
..
config_test.go Consensus: add new "crdt" consensus component 2019-04-17 19:14:26 +02:00
config.go Do not load API components removed from the config (#836) 2019-07-18 17:33:14 +02:00
identity_test.go Tests for identity separation 2019-05-08 21:54:59 +05:30
identity.go Update deps along with go-libp2p-core refactor 2019-06-14 13:10:45 +02:00
util.go config: do not handle "" durations (and do not error) 2019-01-12 18:40:00 +01:00