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

Allow update from no key manager to with key manager #3802

Closed
kostko opened this issue Mar 18, 2021 · 1 comment · Fixed by #3846
Closed

Allow update from no key manager to with key manager #3802

kostko opened this issue Mar 18, 2021 · 1 comment · Fixed by #3846
Assignees
Labels
c:breaking/consensus Category: breaking consensus changes c:registry Category: entity/node/runtime registry service

Comments

@kostko
Copy link
Member

kostko commented Mar 18, 2021

We should allow runtimes to update their descriptors from "no key manager" to "with key manager". Currently such updates are rejected, but would be useful for cases where a runtime starts as non-confidential but then transitions to being confidential.

@kostko kostko added c:breaking/consensus Category: breaking consensus changes c:registry Category: entity/node/runtime registry service labels Mar 18, 2021
@kostko kostko self-assigned this Apr 9, 2021
@kostko
Copy link
Member Author

kostko commented Apr 9, 2021

Done in #3846.

@kostko kostko closed this as completed Apr 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:breaking/consensus Category: breaking consensus changes c:registry Category: entity/node/runtime registry service
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant