-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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: remove writable gateway #9743
Conversation
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.
Thanks!
before we merge, we need to add log.Fatal
so users which have Gateway.Writable: true
get clear, actionable error pointing at ipfs/specs#375
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.
💭 I think sharness timeouts because I've changed the stdout for Gateway and RPC API, and something is naively grepping for old strings. If we don't circle back to this, and want to ship deprecation with Kubo 0.20 rc1, fine to undo 17b5649 for now and restore (readonly)
.
- (readonly) is confusing since we have Gateway.NoFetch - better to remove it from stdout - more actionable error message and docs
- removed (readonly) from gateway (less confusing that having that and Gateway.NoFetch:true at the same time) - RPC API instead of plain API
@lidel sharness was timing out everywhere and was fixed on #9755. I just rebased and it works fine now. |
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.
Thanks!
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.
So much red lines, I love it.
Completely removes the writable gateway, closes #9738.
It was already deprecating and we were already pointing users at the new IPIP PR. Therefore, I decided to remove it completely and mark it as removed in the documentation.
I think that keeping the option there, as per #9738 (comment), could generate confusion, since it would be between a deprecated and removed state that would not be clear.