-
Notifications
You must be signed in to change notification settings - Fork 507
feat: canister metadata via management canister #6069
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
base: master
Are you sure you want to change the base?
Conversation
🤖 Here's your preview: https://yvncx-qyaaa-aaaam-aeiqa-cai.icp0.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.
While we don't expect transferred cycles, I expect that we will charge the canister for calling the API?
The caller will be charged the same fees as for every inter-canister call:
|
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.
Let's do this.
controllers : vec principal; | ||
}; | ||
|
||
type canister_metadata_args = record { |
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.
This PR should be merged when the roll-out is complete and changelog should be updated before merging.
Added explanations for canister metadata errors. Related PRs: - dfinity/ic#6725 - #6069
This PR specifies a new management canister endpoint
canister_metadata
providing canister metadata (contained in custom sections). So far canister metadata are only available to external users via the (certified) state tree (by making a read state HTTP request). The new management canister endpoint makes canister metadata available to other canisters, too.