Skip to content
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!: unify executor data model #4596

Closed

Conversation

0x009922
Copy link
Contributor

Description

This PR solves a few problems:

  • Allows executor define its config parameters through a single ExecutorDataModel entity.
  • Unifies parameters and permission tokens to ExecutorDataModelObject trait, having a definition_id and an arbitrary JSON payload (possible to support SCALE too): dynamic parameter value #4352
  • Parameters no longer configure Sumeragi/WASM/limits. I.e. chain wide configuration could only be set through the config file. It is temporary: this PR is a preparation for a proper implementation of chain-wide configuration: [discussion] Align configuration-related instructions with the RFC #4028
  • Removes extra PermissionTokenSchemaUpdated event. Since this action only happens during executor migration, which emits its own event ExecutorEvent::Upgraded, I also included the updated ExecutorDataModel in this event.

Linked issue

Closes #4352

Signed-off-by: Dmitry Balashov <43530070+0x009922@users.noreply.github.com>
@0x009922 0x009922 self-assigned this May 16, 2024
@github-actions github-actions bot added the api-changes Changes in the API for client libraries label May 16, 2024
@0x009922 0x009922 changed the title refactor!: unify executor data model feat!: unify executor data model May 16, 2024
@0x009922
Copy link
Contributor Author

0x009922 commented May 16, 2024

GitHub doesn't see my updated after force push... closing to reopen as #4597

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api-changes Changes in the API for client libraries
Projects
None yet
Development

Successfully merging this pull request may close these issues.

dynamic parameter value
1 participant