Subscribe "Publish" and "Deploy" events when deploying smartdeploy #46
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
feat: Add events module feat: Enhance events module, usage of IntoKey trait fix: Fix the "publish" event bug ResourceLimitExceeded: Must put the wasm_hash instead of the wasm_binary in the event data
asanson1404
force-pushed
the
feat/subscribe_events
branch
from
28b904f
to
dd81a61
Compare
willemneal
approved these changes
May 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Run an autonomous subscription when smartdeploy is deployed. The indexer can start indexing at the second smartdeploy is online.
Requirements
Must edit a .env file with the Mercury token access (and all the environment variables needed by smartdeploy). This token change every 7 days... :/