feat!: support new CallParameters and generate particle token [NET-767] #2099
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
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.
BEGIN_COMMIT_OVERRIDE
feat: support new CallParameters and generate particle token [NET-767]
END_COMMIT_OVERRIDE
Description
Support new CallParameters and generate particle token
Motivation
We need this to secure the Particle Vault. The particle token will be used in the vault path, ensuring that no one will know about it.
Proposed Changes
Additional Notes
call_functionfunction. It's used by the system-service deployer and by nox when it communicates with the spell service to set trigger info, update counter, and so on.