-
Notifications
You must be signed in to change notification settings - Fork 516
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
Discover Features Protocol: v1_0 refactoring and v2_0 implementation #1500
Discover Features Protocol: v1_0 refactoring and v2_0 implementation #1500
Conversation
Signed-off-by: Shaanjot Gill <[email protected]>
…t-python into discover-feature-v2
Signed-off-by: Shaanjot Gill <[email protected]>
Signed-off-by: Shaanjot Gill <[email protected]>
Signed-off-by: Shaanjot Gill <[email protected]>
…t-python into discover-feature-v2
Signed-off-by: Shaanjot Gill <[email protected]>
Signed-off-by: Shaanjot Gill <[email protected]>
Signed-off-by: Shaanjot Gill <[email protected]>
Signed-off-by: Shaanjot Gill <[email protected]>
Signed-off-by: Shaanjot Gill <[email protected]>
Signed-off-by: Shaanjot Gill <[email protected]>
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.
Just one small question, but overall looks good to me.
|
||
def determine_goal_codes(self) -> Sequence[str]: | ||
"""Return defined goal_codes.""" | ||
return [] |
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.
Should this return goal_codes_matching_query()
?
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.
In the context of GoalCodeRepository
, I am using controller
to play a similar role to message_types
(with ProtocolsRegistry), determine_goal_code
is returning the specified goal-codes
for that protocol to build up the registry and then goal_codes_matching_query
is called upon in there. I don't think we should be returning goal_codes_matching_query
inside determine_goal_codes
.
May be, I can rename determine_goal_codes
to return_goal_codes
to avoid any confusion?
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.
@shaangill025 it's fine you don't need to change it, PR is approved :-)
Earlier implementation involved calling
/featues
endpoint [underserver
tag] to disclose protocols for that agent. It did not involve the flow ofAries
messages as specified in the RFC.Major Changes
--auto-disclose-features
Enables proactive disclosure for v2.0. Such agent will automatically disclose features to another agent when an active connection gets established.--disclose-features-list
can be used to limit what to disclose and if not specified, then all are disclosed.--disclose-features-list
Provides control over what features to publish. Accepts a path to YAML config file [example structure below]. This is valid for both v1.0 and v2.0/features under server
endpointdiscover-features
tagdiscover-features v2.0
tagYAML config file structure, such agent will only disclose
did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/action-menu/1.0
protocol and/oraries.vc
goal-codeTesting
/discover-features/query
. If noconnection_id
is specified then it processes the query on the same agent (disclose features of the same agent). This essentially mimics what can be achieved using/features
[underserver
]. To look up either all records or a record byconnection_id
, use/discover-features/records
./discover-features-2.0/queries
. Same logic when noconnection_id
is specified as above. To look up either all records or a record byconnection_id
, use/discover-features-2.0/records
.connection_id
is an unique identifier for these records.