-
Notifications
You must be signed in to change notification settings - Fork 13
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
Remove auto-migration logic for subscriptions #64
Conversation
Fixes hyperledger#62 Signed-off-by: Andrew Richardson <andrew.richardson@kaleido.io>
Signed-off-by: Andrew Richardson <andrew.richardson@kaleido.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.
Closes #62 |
Also for the record - the manual migration process is to bring the connector down, delete its event stream, then bring it back up and wait for it to recreate the event stream (which will contain a single "base" subscription). Then, for each pool on each erc1155 connector, make this manual POST:
Note that the protocol ID for this connector will look something like "F1" or "N2". This call should cause 4 additional subscriptions (per pool) to be added to the event stream. |
Signed-off-by: Andrew Richardson <andrew.richardson@kaleido.io>
09db60d
to
7b248d4
Compare
Signed-off-by: Andrew Richardson <andrew.richardson@kaleido.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.
👍
The ERC1155 connector currently attempts to detect when event subscriptions need to be deleted and recreated
(for instance, because new events are now supported and require new subscriptions). While this can be convenient,
it also has the potential to cause negative side effects if the new subscriptions fail to create.
Remove the auto-migration path and downgrade this situation to a warning log. This means it will require manual
intervention from a user if (in the future) we add features that require subscriptions to be recreated.