-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: api support for ipfs-cluster@1.0 #1789
Conversation
The IPFS Cluster v1 release has much improved perf, and some breaking API changes. In this PR we upgrade the ipfs-cluster client and local test environment to work with the v1 cluster API. see: #1736 see: https://github.com/nftstorage/ipfs-cluster/releases/tag/v5.0.0 License: (Apache-2.0 AND MIT) Signed-off-by: Oli Evans <oli@tableflip.io>
Deploying with Cloudflare Pages
|
@gobengo CI is failing on this PR with
It looks like this was introduced with #1698 |
the secrets context is not available in `jobs.<job id>.if` see: https://docs.github.com/en/actions/learn-github-actions/contexts#context-availability License: (Apache-2.0 AND MIT) Signed-off-by: Oli Evans <oli@tableflip.io>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cluster related changes look good. secrets change still doesn't make as it looks like dev deploy fails. I will check and see if understand why this if
is in use here
@olizilla big apologies! I should have tested all the workflows since I touched them. Is there a better way than briefly updating some file in each project? Here is another approach that might work? #1791 @vasco-santos if you're still looking, wdyt of that? |
I added the conditional to make PRs pass this check even if coming from forks that don't have that variable defined. I had a PR from my fork that was failing due to it. I think something else is going on where the existing secret.CF_API_TOKEN is defined in this repo but erroring against CF API. i.e. it's potentially invalid (or CF API is rejecting it, but that seems less likely). |
* remove secrets check in if: in github api workflow * touch api package to trigger github action * ci(api): Try another way of deploy-dev not breaking if CF_API_TOKEN is not set * ci(api): temporarily make deploy-dev not need test * Revert "touch api package to trigger github action" This reverts commit 1f110d1. * Revert "ci(api): temporarily make deploy-dev not need test" This reverts commit d09c94f. * feat: api support for ipfs-cluster@1.0 The IPFS Cluster v1 release has much improved perf, and some breaking API changes. In this PR we upgrade the ipfs-cluster client and local test environment to work with the v1 cluster API. see: #1736 see: https://github.com/nftstorage/ipfs-cluster/releases/tag/v5.0.0 License: (Apache-2.0 AND MIT) Signed-off-by: Oli Evans <oli@tableflip.io> Co-authored-by: Oli Evans <oli@tableflip.io>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Same as web3-storage/web3.storage#1241 to go together with #1789
The IPFS Cluster v1 release has much improved perf, and some breaking API changes.
In this PR we upgrade the ipfs-cluster client and local test environment to work with the v1 cluster API.
CI was failing for the API, so this PR includes a change to that workflow to fix that.
After merging this PR
see: #1736
see: https://github.com/nftstorage/ipfs-cluster/releases/tag/v5.0.0
License: (Apache-2.0 AND MIT)
Signed-off-by: Oli Evans oli@tableflip.io