cascade/ipfs-cluster
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
f213fe3dfa
ipfs-cluster/version/version.go

20 lines
673 B
Go
Raw Normal View History

Fix #382: Extract headers from IPFS API requests & apply them to hijacked ones. This commit makes the proxy extract useful fixed headers (like CORS) from the IPFS daemon API responses and then apply them to the responses from hijacked endpoints like /add or /repo/stat. It does this by caching a list of headers from the first IPFS API response which has them. If we have not performed any proxied request or managed to obtain the headers we're interested in, this will try triggering a request to "/api/v0/version" to obtain them first. This should fix the issues with using Cluster proxy with IPFS Companion and Chrome. License: MIT Signed-off-by: Hector Sanjuan <code@hector.link>
2018-12-18 14:44:11 +00:00
package version
Issue-21: Add cluster ID() method License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
2017-01-24 15:19:23 +00:00
Allow running peers with different cluster versions in the same cluster This patch modifies the RPC protocol tag to use Major and Minor parts of the version and not all of it. This means all peers on the 0.5.x can run in the same cluster. As cluster has become more mature and I see less risks in letting peers from similar versions run together. This is useful when upgrading too. License: MIT Signed-off-by: Hector Sanjuan <code@hector.link>
2018-09-26 15:45:02 +00:00
import (
semver "github.com/blang/semver"
staticcheck: fix all staticcheck warnings in the project
2020-04-14 17:58:00 +00:00
protocol "github.com/libp2p/go-libp2p-core/protocol"
Allow running peers with different cluster versions in the same cluster This patch modifies the RPC protocol tag to use Major and Minor parts of the version and not all of it. This means all peers on the 0.5.x can run in the same cluster. As cluster has become more mature and I see less risks in letting peers from similar versions run together. This is useful when upgrading too. License: MIT Signed-off-by: Hector Sanjuan <code@hector.link>
2018-09-26 15:45:02 +00:00
)
Set the RPC Protocol Version to a fixed value The RPC endpoints no longer change much, but every minor release enforces that all peers in a Cluster must run on the same version. This was meant to allow greater flexibility when upgrading the RPC endpoints. Now we should not be in a situation that releasing a minor cluster version causes peers incompatibilities, even though nothing changes on the RPC side of things. Therefore we make 0.12 the RPC protocol version going forward and detach it from the actual cluster version from this point.
2020-04-23 17:08:11 +00:00
// Version is the current cluster version.
Set development version v0.13.0-dev
2020-05-19 08:08:09 +00:00
var Version = semver.MustParse("0.13.0-dev")
Issue-21: Add cluster ID() method License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
2017-01-24 15:19:23 +00:00
Set the RPC Protocol Version to a fixed value The RPC endpoints no longer change much, but every minor release enforces that all peers in a Cluster must run on the same version. This was meant to allow greater flexibility when upgrading the RPC endpoints. Now we should not be in a situation that releasing a minor cluster version causes peers incompatibilities, even though nothing changes on the RPC side of things. Therefore we make 0.12 the RPC protocol version going forward and detach it from the actual cluster version from this point.
2020-04-23 17:08:11 +00:00
// RPCProtocol is protocol handler used to send libp2p-rpc messages between
// cluster peers. All peers in the cluster need to speak the same protocol
// version.
//
// The RPC Protocol is not linked to the IPFS Cluster version (though it once
// was). The protocol version will be updated as needed when breaking changes
// are introduced, though at this point we aim to minimize those as much as
// possible.
var RPCProtocol = protocol.ID("/ipfscluster/0.12/rpc")
Reference in New Issue Copy Permalink