-
Notifications
You must be signed in to change notification settings - Fork 17
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
Add support for custom packages #717
Conversation
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.
With custom package type you can define you a custom package for a skill or an agent. The custom package should be defined via a component.yaml
file. The config file should look like this
name: comonent
author: valory
version: 0.1.0
type: custom
description: The custom component package.
license: Apache-2.0
aea_version: '>=1.0.0, <2.0.0'
fingerprint:
__init__.py: bafybeidey4syohls5hxmso6qsp5p4uhtzle5txv2mlbym6ktjzknich6oa
kelly_criterion.py: bafybeibqwl52cnz64cysjd2jnjijuakdvyrffapxq65cdzx6g65gu42deq
fingerprint_ignore_patterns: []
dependencies: {}
The custom component also allows you to define extra parameters like here. At the runtime you can access these parameters using component.get
method. Eg component.get("entry_point")
These components can be defined as a dependencies for skill and agent packages to manage python dependencies.
(...)
customs:
- valory/component:0.1.0:bafybeib3mrksfhsym4xktqx44vbpbtbcl57l3tfjh5ev7k6g27pqa4grmy
(...)
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #717 +/- ##
==========================================
- Coverage 90.29% 90.26% -0.03%
==========================================
Files 371 373 +2
Lines 29807 29854 +47
==========================================
+ Hits 26914 26949 +35
- Misses 2893 2905 +12
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
You can also scaffold custom components using |
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.
Before merging this, please ensure it works downstream in open-autonomy and also in mech
repo where there are custom packages already
Proposed changes
This PR
Fixes
fixes #706
Types of changes
What types of changes does your code introduce to agents-aea?
Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply.develop
branch (left side). Also you should start your branch off ourdevelop
.