feat(host): remove requirement for actors to have capabilities in claims #1388
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
Signed-off-by: Connor Smith <connor.smith.256@gmail.com>
connorsmith256
force-pushed
the
feat/drop-capability-claims-requirement
branch
from
3fcb943
to
7f65a6f
Compare
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.
Feature or Problem
This removes the requirement for actors to include capabilities in their claims. For components, the wit interfaces describe this information, and runtime links are now the way an operator signals intent for components to be able to communicate
Related Issues
Implements changes described in #1219
Release Information
Next
Consumer Impact
N/A. We can remove/stop parsing the
claimsfromActorConfigin wash, once a host with this feature is releasedTesting
Unit Test(s)
Acceptance or Integration
Manual Verification