aigency 0.0.1rc15474277__tar.gz → 0.0.1rc235167702__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- aigency-0.0.1rc235167702/PKG-INFO +267 -0
- aigency-0.0.1rc235167702/README.md +255 -0
- {aigency-0.0.1rc15474277 → aigency-0.0.1rc235167702}/aigency/agents/generator.py +21 -19
- aigency-0.0.1rc235167702/aigency/schemas/agent/agent.py +12 -0
- aigency-0.0.1rc235167702/aigency/schemas/agent/model.py +12 -0
- aigency-0.0.1rc235167702/aigency/schemas/agent/skills.py +10 -0
- aigency-0.0.1rc235167702/aigency/schemas/aigency_config.py +14 -0
- aigency-0.0.1rc235167702/aigency/schemas/metadata/metadata.py +8 -0
- aigency-0.0.1rc235167702/aigency/schemas/observability/observability.py +10 -0
- aigency-0.0.1rc235167702/aigency/schemas/observability/phoenix.py +6 -0
- aigency-0.0.1rc235167702/aigency/schemas/service/capabilities.py +5 -0
- aigency-0.0.1rc235167702/aigency/schemas/service/interface.py +7 -0
- aigency-0.0.1rc235167702/aigency/schemas/service/service.py +9 -0
- {aigency-0.0.1rc15474277 → aigency-0.0.1rc235167702}/aigency/tools/generator.py +3 -7
- {aigency-0.0.1rc15474277 → aigency-0.0.1rc235167702}/aigency/utils/config_service.py +38 -17
- aigency-0.0.1rc235167702/aigency.egg-info/PKG-INFO +267 -0
- aigency-0.0.1rc235167702/aigency.egg-info/SOURCES.txt +26 -0
- {aigency-0.0.1rc15474277 → aigency-0.0.1rc235167702}/pyproject.toml +1 -1
- aigency-0.0.1rc15474277/PKG-INFO +0 -267
- aigency-0.0.1rc15474277/README.md +0 -255
- aigency-0.0.1rc15474277/aigency/models/config.py +0 -69
- aigency-0.0.1rc15474277/aigency/models/core.py +0 -28
- aigency-0.0.1rc15474277/aigency.egg-info/PKG-INFO +0 -267
- aigency-0.0.1rc15474277/aigency.egg-info/SOURCES.txt +0 -18
- {aigency-0.0.1rc15474277 → aigency-0.0.1rc235167702}/aigency/__init__.py +0 -0
- {aigency-0.0.1rc15474277 → aigency-0.0.1rc235167702}/aigency/agents/executor.py +0 -0
- {aigency-0.0.1rc15474277/aigency/models → aigency-0.0.1rc235167702/aigency/schemas/agent}/tools.py +0 -0
- {aigency-0.0.1rc15474277 → aigency-0.0.1rc235167702}/aigency/utils/logger.py +0 -0
- {aigency-0.0.1rc15474277 → aigency-0.0.1rc235167702}/aigency/utils/singleton.py +0 -0
- {aigency-0.0.1rc15474277 → aigency-0.0.1rc235167702}/aigency/utils/utils.py +0 -0
- {aigency-0.0.1rc15474277 → aigency-0.0.1rc235167702}/aigency.egg-info/dependency_links.txt +0 -0
- {aigency-0.0.1rc15474277 → aigency-0.0.1rc235167702}/aigency.egg-info/requires.txt +0 -0
- {aigency-0.0.1rc15474277 → aigency-0.0.1rc235167702}/aigency.egg-info/top_level.txt +0 -0
- {aigency-0.0.1rc15474277 → aigency-0.0.1rc235167702}/setup.cfg +0 -0
@@ -0,0 +1,267 @@
|
|
1
|
+
Metadata-Version: 2.4
|
2
|
+
Name: aigency
|
3
|
+
Version: 0.0.1rc235167702
|
4
|
+
Summary: Add your description here
|
5
|
+
Requires-Python: >=3.12
|
6
|
+
Description-Content-Type: text/markdown
|
7
|
+
Requires-Dist: google-adk>=1.11.0
|
8
|
+
Requires-Dist: a2a-sdk==0.3.0
|
9
|
+
Requires-Dist: litellm<1.73.0,>=1.72.6
|
10
|
+
Requires-Dist: pyyaml==6.0.2
|
11
|
+
Requires-Dist: PyJWT==2.10.1
|
12
|
+
|
13
|
+
# aigency-lib
|
14
|
+
|
15
|
+
A library for creating and managing AI agents.
|
16
|
+
|
17
|
+
## Quick Start
|
18
|
+
|
19
|
+
To test a simple agent:
|
20
|
+
|
21
|
+
```bash
|
22
|
+
cd examples/simple_agents/hello_world_agent
|
23
|
+
docker compose up
|
24
|
+
```
|
25
|
+
|
26
|
+
## 🔧 Version Management
|
27
|
+
|
28
|
+
This project includes an automated system for managing versions in both development and production.
|
29
|
+
|
30
|
+
### Version Manager
|
31
|
+
|
32
|
+
The `scripts/version_manager.py` script helps you manage your package versions locally.
|
33
|
+
|
34
|
+
#### Available Commands
|
35
|
+
|
36
|
+
##### 1. View current information
|
37
|
+
```bash
|
38
|
+
python scripts/version_manager.py show
|
39
|
+
```
|
40
|
+
**What it does:**
|
41
|
+
- Shows the current version in `pyproject.toml`
|
42
|
+
- Shows the current git branch
|
43
|
+
- Shows the current commit
|
44
|
+
- If you're not on `main`, suggests a development version
|
45
|
+
|
46
|
+
**Example output:**
|
47
|
+
```
|
48
|
+
Current version: 0.0.1
|
49
|
+
Branch: feature/new-agent
|
50
|
+
Commit: a1b2c3d
|
51
|
+
Suggested dev version: 0.0.1.dev20250409143022+feature/new-agent.a1b2c3d
|
52
|
+
```
|
53
|
+
|
54
|
+
##### 2. Create development version
|
55
|
+
```bash
|
56
|
+
python scripts/version_manager.py dev
|
57
|
+
```
|
58
|
+
**What it does:**
|
59
|
+
- Takes the current version and creates a development version
|
60
|
+
- Format: `version.devYYYYMMDDHHMMSS+branch.commit`
|
61
|
+
- Automatically updates the `pyproject.toml`
|
62
|
+
|
63
|
+
**Example:**
|
64
|
+
```bash
|
65
|
+
# If you're on branch "feature/auth" with commit "abc123"
|
66
|
+
python scripts/version_manager.py dev
|
67
|
+
# Result: 0.0.1.dev20250409143022
|
68
|
+
```
|
69
|
+
|
70
|
+
##### 3. Set specific version
|
71
|
+
```bash
|
72
|
+
python scripts/version_manager.py set --version "0.1.0"
|
73
|
+
```
|
74
|
+
**What it does:**
|
75
|
+
- Changes the version to the one you specify
|
76
|
+
- Useful for releases or to fix versions
|
77
|
+
|
78
|
+
**Examples:**
|
79
|
+
```bash
|
80
|
+
# Release version
|
81
|
+
python scripts/version_manager.py set --version "1.0.0"
|
82
|
+
|
83
|
+
# Beta version
|
84
|
+
python scripts/version_manager.py set --version "1.0.0b1"
|
85
|
+
|
86
|
+
# Alpha version
|
87
|
+
python scripts/version_manager.py set --version "1.0.0a1"
|
88
|
+
```
|
89
|
+
|
90
|
+
##### 4. Create Release Candidate version
|
91
|
+
```bash
|
92
|
+
python scripts/version_manager.py rc --version "1.0.1"
|
93
|
+
```
|
94
|
+
**What it does:**
|
95
|
+
- Creates an RC version with the format `version-rc<commit>`
|
96
|
+
- Useful for preparing releases on `release/*` branches
|
97
|
+
|
98
|
+
##### 5. Validate current version
|
99
|
+
```bash
|
100
|
+
python scripts/version_manager.py validate
|
101
|
+
```
|
102
|
+
**What it does:**
|
103
|
+
- Validates that the current version is appropriate for the branch
|
104
|
+
- Verifies semantic format on `main` and `release/*` branches
|
105
|
+
|
106
|
+
##### 6. Create dev with custom base version
|
107
|
+
```bash
|
108
|
+
python scripts/version_manager.py dev --base-version "0.2.0"
|
109
|
+
```
|
110
|
+
**What it does:**
|
111
|
+
- Uses a different base version than the current one
|
112
|
+
- Useful when you want to prepare a dev version for the next release
|
113
|
+
|
114
|
+
### 🚀 Recommended Workflow
|
115
|
+
|
116
|
+
#### For daily development:
|
117
|
+
```bash
|
118
|
+
# 1. View current status
|
119
|
+
python scripts/version_manager.py show
|
120
|
+
|
121
|
+
# 2. If you're on a feature branch, create dev version
|
122
|
+
python scripts/version_manager.py dev
|
123
|
+
|
124
|
+
# 3. Make your changes and commits
|
125
|
+
git add .
|
126
|
+
git commit -m "feat: new functionality"
|
127
|
+
|
128
|
+
# 4. If you need to update the dev version (optional)
|
129
|
+
python scripts/version_manager.py dev
|
130
|
+
```
|
131
|
+
|
132
|
+
#### For releases:
|
133
|
+
```bash
|
134
|
+
# 1. On main branch, set release version
|
135
|
+
python scripts/version_manager.py set --version "1.0.0"
|
136
|
+
|
137
|
+
# 2. Commit the version
|
138
|
+
git add pyproject.toml
|
139
|
+
git commit -m "bump: version 1.0.0"
|
140
|
+
|
141
|
+
# 3. Use GitHub workflow to publish
|
142
|
+
```
|
143
|
+
|
144
|
+
#### For testing:
|
145
|
+
```bash
|
146
|
+
# Create specific test version
|
147
|
+
python scripts/version_manager.py set --version "1.0.0rc1"
|
148
|
+
```
|
149
|
+
|
150
|
+
### ⚠️ PyPI Limitations
|
151
|
+
|
152
|
+
PyPI doesn't allow "local versions" (versions with `+` and local identifiers). That's why we've adapted the format:
|
153
|
+
|
154
|
+
- ❌ Not allowed: `1.0.0.dev20250409+feature.abc123`
|
155
|
+
- ✅ Allowed: `1.0.0.dev20250409`
|
156
|
+
|
157
|
+
**Solution for Release Candidates:**
|
158
|
+
- We convert the commit hash (hexadecimal) to decimal
|
159
|
+
- Example: commit `abc123` → `11256099` → version `1.0.1rc11256099`
|
160
|
+
- This maintains commit uniqueness in a PyPI-compatible format
|
161
|
+
|
162
|
+
**Result:**
|
163
|
+
- Dev versions include unique timestamp
|
164
|
+
- RC versions include commit hash (in decimal)
|
165
|
+
- We maintain traceability without using local versions
|
166
|
+
|
167
|
+
### 📋 Practical Use Cases
|
168
|
+
|
169
|
+
**Scenario 1: Working on a feature**
|
170
|
+
```bash
|
171
|
+
git checkout -b feature/new-auth
|
172
|
+
python scripts/version_manager.py dev
|
173
|
+
# Now you have: 0.0.1.dev20250409143022
|
174
|
+
```
|
175
|
+
|
176
|
+
**Scenario 2: Preparing release**
|
177
|
+
```bash
|
178
|
+
git checkout main
|
179
|
+
python scripts/version_manager.py set --version "1.0.0"
|
180
|
+
git add pyproject.toml
|
181
|
+
git commit -m "release: v1.0.0"
|
182
|
+
```
|
183
|
+
|
184
|
+
**Scenario 3: Preparing Release Candidate**
|
185
|
+
```bash
|
186
|
+
git checkout -b release/1.0.1
|
187
|
+
python scripts/version_manager.py rc --version "1.0.1"
|
188
|
+
# Result: 1.0.1rc12345678 (where 12345678 is the commit hash in decimal)
|
189
|
+
```
|
190
|
+
|
191
|
+
**Scenario 4: Urgent hotfix**
|
192
|
+
```bash
|
193
|
+
git checkout -b hotfix/critical-bug
|
194
|
+
python scripts/version_manager.py dev --base-version "1.0.1"
|
195
|
+
# Result: 1.0.1.dev20250409143022
|
196
|
+
```
|
197
|
+
|
198
|
+
## 🔄 Intelligent CI/CD Workflow
|
199
|
+
|
200
|
+
The project includes a single intelligent workflow (`python-publish.yml`) that automatically handles different version types based on the branch:
|
201
|
+
|
202
|
+
### Automatic behavior by branch:
|
203
|
+
|
204
|
+
#### 🚀 `main` Branch - Production Versions
|
205
|
+
- **Trigger**: Push to `main` or manual execution
|
206
|
+
- **Version**: Uses exactly the version from `pyproject.toml`
|
207
|
+
- **Validations**:
|
208
|
+
- ✅ Verifies it's a valid semantic version (e.g.: `1.0.0`)
|
209
|
+
- ✅ Verifies it doesn't already exist on PyPI
|
210
|
+
- ❌ Fails if it contains development suffixes (`dev`, `rc`, `alpha`, `beta`)
|
211
|
+
- **Target**: PyPI production
|
212
|
+
|
213
|
+
#### 🎯 `release/*` Branches - Release Candidates
|
214
|
+
- **Trigger**: Push to `release/X.Y.Z` branch or manual execution
|
215
|
+
- **Version**: `X.Y.ZrcN` where N is the commit hash in decimal (e.g.: `1.0.1rc12345678`)
|
216
|
+
- **Validations**:
|
217
|
+
- ✅ Verifies that `X.Y.Z` is a valid semantic version
|
218
|
+
- ✅ Extracts version from branch name
|
219
|
+
- ✅ Uses commit hash as unique identifier
|
220
|
+
- ✅ PyPI-compatible format
|
221
|
+
- **Target**: PyPI production
|
222
|
+
- **Example**: Branch `release/1.0.1` + commit `abc123` → Version `1.0.1rc11256099`
|
223
|
+
|
224
|
+
#### 🔧 Other Branches - Development Versions
|
225
|
+
- **Trigger**: Push to any other branch or manual execution
|
226
|
+
- **Version**: `current.devYYYYMMDDHHMMSS` (e.g.: `0.0.1.dev20250409143022`)
|
227
|
+
- **Target**: PyPI production
|
228
|
+
- **Note**: No local versions for PyPI compatibility
|
229
|
+
|
230
|
+
### Recommended workflow:
|
231
|
+
|
232
|
+
```bash
|
233
|
+
# 1. Development on feature branch
|
234
|
+
git checkout -b feature/new-functionality
|
235
|
+
# Automatic version: 0.0.1.dev20250409143022+feature-new-functionality.abc123
|
236
|
+
|
237
|
+
# 2. Prepare release
|
238
|
+
git checkout -b release/1.0.0
|
239
|
+
git push origin release/1.0.0
|
240
|
+
# Automatic version: 1.0.0rc12345678
|
241
|
+
|
242
|
+
# 3. Final release
|
243
|
+
git checkout main
|
244
|
+
python scripts/version_manager.py set --version "1.0.0"
|
245
|
+
git add pyproject.toml
|
246
|
+
git commit -m "release: v1.0.0"
|
247
|
+
git push origin main
|
248
|
+
# Version: 1.0.0 (with validations)
|
249
|
+
```
|
250
|
+
|
251
|
+
## 📦 Installation
|
252
|
+
|
253
|
+
```bash
|
254
|
+
pip install aigency
|
255
|
+
```
|
256
|
+
|
257
|
+
## 🛠️ Development
|
258
|
+
|
259
|
+
1. Clone the repository
|
260
|
+
2. Install development dependencies
|
261
|
+
3. Use the version manager to manage versions during development
|
262
|
+
|
263
|
+
```bash
|
264
|
+
git clone <repo-url>
|
265
|
+
cd aigency-lib
|
266
|
+
pip install -e .
|
267
|
+
```
|
@@ -0,0 +1,255 @@
|
|
1
|
+
# aigency-lib
|
2
|
+
|
3
|
+
A library for creating and managing AI agents.
|
4
|
+
|
5
|
+
## Quick Start
|
6
|
+
|
7
|
+
To test a simple agent:
|
8
|
+
|
9
|
+
```bash
|
10
|
+
cd examples/simple_agents/hello_world_agent
|
11
|
+
docker compose up
|
12
|
+
```
|
13
|
+
|
14
|
+
## 🔧 Version Management
|
15
|
+
|
16
|
+
This project includes an automated system for managing versions in both development and production.
|
17
|
+
|
18
|
+
### Version Manager
|
19
|
+
|
20
|
+
The `scripts/version_manager.py` script helps you manage your package versions locally.
|
21
|
+
|
22
|
+
#### Available Commands
|
23
|
+
|
24
|
+
##### 1. View current information
|
25
|
+
```bash
|
26
|
+
python scripts/version_manager.py show
|
27
|
+
```
|
28
|
+
**What it does:**
|
29
|
+
- Shows the current version in `pyproject.toml`
|
30
|
+
- Shows the current git branch
|
31
|
+
- Shows the current commit
|
32
|
+
- If you're not on `main`, suggests a development version
|
33
|
+
|
34
|
+
**Example output:**
|
35
|
+
```
|
36
|
+
Current version: 0.0.1
|
37
|
+
Branch: feature/new-agent
|
38
|
+
Commit: a1b2c3d
|
39
|
+
Suggested dev version: 0.0.1.dev20250409143022+feature/new-agent.a1b2c3d
|
40
|
+
```
|
41
|
+
|
42
|
+
##### 2. Create development version
|
43
|
+
```bash
|
44
|
+
python scripts/version_manager.py dev
|
45
|
+
```
|
46
|
+
**What it does:**
|
47
|
+
- Takes the current version and creates a development version
|
48
|
+
- Format: `version.devYYYYMMDDHHMMSS+branch.commit`
|
49
|
+
- Automatically updates the `pyproject.toml`
|
50
|
+
|
51
|
+
**Example:**
|
52
|
+
```bash
|
53
|
+
# If you're on branch "feature/auth" with commit "abc123"
|
54
|
+
python scripts/version_manager.py dev
|
55
|
+
# Result: 0.0.1.dev20250409143022
|
56
|
+
```
|
57
|
+
|
58
|
+
##### 3. Set specific version
|
59
|
+
```bash
|
60
|
+
python scripts/version_manager.py set --version "0.1.0"
|
61
|
+
```
|
62
|
+
**What it does:**
|
63
|
+
- Changes the version to the one you specify
|
64
|
+
- Useful for releases or to fix versions
|
65
|
+
|
66
|
+
**Examples:**
|
67
|
+
```bash
|
68
|
+
# Release version
|
69
|
+
python scripts/version_manager.py set --version "1.0.0"
|
70
|
+
|
71
|
+
# Beta version
|
72
|
+
python scripts/version_manager.py set --version "1.0.0b1"
|
73
|
+
|
74
|
+
# Alpha version
|
75
|
+
python scripts/version_manager.py set --version "1.0.0a1"
|
76
|
+
```
|
77
|
+
|
78
|
+
##### 4. Create Release Candidate version
|
79
|
+
```bash
|
80
|
+
python scripts/version_manager.py rc --version "1.0.1"
|
81
|
+
```
|
82
|
+
**What it does:**
|
83
|
+
- Creates an RC version with the format `version-rc<commit>`
|
84
|
+
- Useful for preparing releases on `release/*` branches
|
85
|
+
|
86
|
+
##### 5. Validate current version
|
87
|
+
```bash
|
88
|
+
python scripts/version_manager.py validate
|
89
|
+
```
|
90
|
+
**What it does:**
|
91
|
+
- Validates that the current version is appropriate for the branch
|
92
|
+
- Verifies semantic format on `main` and `release/*` branches
|
93
|
+
|
94
|
+
##### 6. Create dev with custom base version
|
95
|
+
```bash
|
96
|
+
python scripts/version_manager.py dev --base-version "0.2.0"
|
97
|
+
```
|
98
|
+
**What it does:**
|
99
|
+
- Uses a different base version than the current one
|
100
|
+
- Useful when you want to prepare a dev version for the next release
|
101
|
+
|
102
|
+
### 🚀 Recommended Workflow
|
103
|
+
|
104
|
+
#### For daily development:
|
105
|
+
```bash
|
106
|
+
# 1. View current status
|
107
|
+
python scripts/version_manager.py show
|
108
|
+
|
109
|
+
# 2. If you're on a feature branch, create dev version
|
110
|
+
python scripts/version_manager.py dev
|
111
|
+
|
112
|
+
# 3. Make your changes and commits
|
113
|
+
git add .
|
114
|
+
git commit -m "feat: new functionality"
|
115
|
+
|
116
|
+
# 4. If you need to update the dev version (optional)
|
117
|
+
python scripts/version_manager.py dev
|
118
|
+
```
|
119
|
+
|
120
|
+
#### For releases:
|
121
|
+
```bash
|
122
|
+
# 1. On main branch, set release version
|
123
|
+
python scripts/version_manager.py set --version "1.0.0"
|
124
|
+
|
125
|
+
# 2. Commit the version
|
126
|
+
git add pyproject.toml
|
127
|
+
git commit -m "bump: version 1.0.0"
|
128
|
+
|
129
|
+
# 3. Use GitHub workflow to publish
|
130
|
+
```
|
131
|
+
|
132
|
+
#### For testing:
|
133
|
+
```bash
|
134
|
+
# Create specific test version
|
135
|
+
python scripts/version_manager.py set --version "1.0.0rc1"
|
136
|
+
```
|
137
|
+
|
138
|
+
### ⚠️ PyPI Limitations
|
139
|
+
|
140
|
+
PyPI doesn't allow "local versions" (versions with `+` and local identifiers). That's why we've adapted the format:
|
141
|
+
|
142
|
+
- ❌ Not allowed: `1.0.0.dev20250409+feature.abc123`
|
143
|
+
- ✅ Allowed: `1.0.0.dev20250409`
|
144
|
+
|
145
|
+
**Solution for Release Candidates:**
|
146
|
+
- We convert the commit hash (hexadecimal) to decimal
|
147
|
+
- Example: commit `abc123` → `11256099` → version `1.0.1rc11256099`
|
148
|
+
- This maintains commit uniqueness in a PyPI-compatible format
|
149
|
+
|
150
|
+
**Result:**
|
151
|
+
- Dev versions include unique timestamp
|
152
|
+
- RC versions include commit hash (in decimal)
|
153
|
+
- We maintain traceability without using local versions
|
154
|
+
|
155
|
+
### 📋 Practical Use Cases
|
156
|
+
|
157
|
+
**Scenario 1: Working on a feature**
|
158
|
+
```bash
|
159
|
+
git checkout -b feature/new-auth
|
160
|
+
python scripts/version_manager.py dev
|
161
|
+
# Now you have: 0.0.1.dev20250409143022
|
162
|
+
```
|
163
|
+
|
164
|
+
**Scenario 2: Preparing release**
|
165
|
+
```bash
|
166
|
+
git checkout main
|
167
|
+
python scripts/version_manager.py set --version "1.0.0"
|
168
|
+
git add pyproject.toml
|
169
|
+
git commit -m "release: v1.0.0"
|
170
|
+
```
|
171
|
+
|
172
|
+
**Scenario 3: Preparing Release Candidate**
|
173
|
+
```bash
|
174
|
+
git checkout -b release/1.0.1
|
175
|
+
python scripts/version_manager.py rc --version "1.0.1"
|
176
|
+
# Result: 1.0.1rc12345678 (where 12345678 is the commit hash in decimal)
|
177
|
+
```
|
178
|
+
|
179
|
+
**Scenario 4: Urgent hotfix**
|
180
|
+
```bash
|
181
|
+
git checkout -b hotfix/critical-bug
|
182
|
+
python scripts/version_manager.py dev --base-version "1.0.1"
|
183
|
+
# Result: 1.0.1.dev20250409143022
|
184
|
+
```
|
185
|
+
|
186
|
+
## 🔄 Intelligent CI/CD Workflow
|
187
|
+
|
188
|
+
The project includes a single intelligent workflow (`python-publish.yml`) that automatically handles different version types based on the branch:
|
189
|
+
|
190
|
+
### Automatic behavior by branch:
|
191
|
+
|
192
|
+
#### 🚀 `main` Branch - Production Versions
|
193
|
+
- **Trigger**: Push to `main` or manual execution
|
194
|
+
- **Version**: Uses exactly the version from `pyproject.toml`
|
195
|
+
- **Validations**:
|
196
|
+
- ✅ Verifies it's a valid semantic version (e.g.: `1.0.0`)
|
197
|
+
- ✅ Verifies it doesn't already exist on PyPI
|
198
|
+
- ❌ Fails if it contains development suffixes (`dev`, `rc`, `alpha`, `beta`)
|
199
|
+
- **Target**: PyPI production
|
200
|
+
|
201
|
+
#### 🎯 `release/*` Branches - Release Candidates
|
202
|
+
- **Trigger**: Push to `release/X.Y.Z` branch or manual execution
|
203
|
+
- **Version**: `X.Y.ZrcN` where N is the commit hash in decimal (e.g.: `1.0.1rc12345678`)
|
204
|
+
- **Validations**:
|
205
|
+
- ✅ Verifies that `X.Y.Z` is a valid semantic version
|
206
|
+
- ✅ Extracts version from branch name
|
207
|
+
- ✅ Uses commit hash as unique identifier
|
208
|
+
- ✅ PyPI-compatible format
|
209
|
+
- **Target**: PyPI production
|
210
|
+
- **Example**: Branch `release/1.0.1` + commit `abc123` → Version `1.0.1rc11256099`
|
211
|
+
|
212
|
+
#### 🔧 Other Branches - Development Versions
|
213
|
+
- **Trigger**: Push to any other branch or manual execution
|
214
|
+
- **Version**: `current.devYYYYMMDDHHMMSS` (e.g.: `0.0.1.dev20250409143022`)
|
215
|
+
- **Target**: PyPI production
|
216
|
+
- **Note**: No local versions for PyPI compatibility
|
217
|
+
|
218
|
+
### Recommended workflow:
|
219
|
+
|
220
|
+
```bash
|
221
|
+
# 1. Development on feature branch
|
222
|
+
git checkout -b feature/new-functionality
|
223
|
+
# Automatic version: 0.0.1.dev20250409143022+feature-new-functionality.abc123
|
224
|
+
|
225
|
+
# 2. Prepare release
|
226
|
+
git checkout -b release/1.0.0
|
227
|
+
git push origin release/1.0.0
|
228
|
+
# Automatic version: 1.0.0rc12345678
|
229
|
+
|
230
|
+
# 3. Final release
|
231
|
+
git checkout main
|
232
|
+
python scripts/version_manager.py set --version "1.0.0"
|
233
|
+
git add pyproject.toml
|
234
|
+
git commit -m "release: v1.0.0"
|
235
|
+
git push origin main
|
236
|
+
# Version: 1.0.0 (with validations)
|
237
|
+
```
|
238
|
+
|
239
|
+
## 📦 Installation
|
240
|
+
|
241
|
+
```bash
|
242
|
+
pip install aigency
|
243
|
+
```
|
244
|
+
|
245
|
+
## 🛠️ Development
|
246
|
+
|
247
|
+
1. Clone the repository
|
248
|
+
2. Install development dependencies
|
249
|
+
3. Use the version manager to manage versions during development
|
250
|
+
|
251
|
+
```bash
|
252
|
+
git clone <repo-url>
|
253
|
+
cd aigency-lib
|
254
|
+
pip install -e .
|
255
|
+
```
|
@@ -10,7 +10,7 @@ from google.adk.runners import Runner
|
|
10
10
|
from google.adk.sessions import InMemorySessionService
|
11
11
|
|
12
12
|
from aigency.agents.executor import AgentA2AExecutor
|
13
|
-
from aigency.
|
13
|
+
from aigency.schemas.aigency_config import AigencyConfig
|
14
14
|
from aigency.tools.generator import ToolGenerator
|
15
15
|
|
16
16
|
|
@@ -18,22 +18,26 @@ class AgentA2AGenerator:
|
|
18
18
|
"""Generator for creating A2A agents and related components."""
|
19
19
|
|
20
20
|
@staticmethod
|
21
|
-
def create_agent(agent_config:
|
21
|
+
def create_agent(agent_config: AigencyConfig) -> Agent:
|
22
|
+
|
23
|
+
tools = [
|
24
|
+
ToolGenerator.create_tool(tool_cfg) for tool_cfg in agent_config.agent.tools
|
25
|
+
]
|
22
26
|
|
23
|
-
tools = [ToolGenerator.create_tool(tool_cfg) for tool_cfg in agent_config.tools]
|
24
|
-
|
25
27
|
return Agent(
|
26
|
-
name=agent_config.name,
|
27
|
-
model=agent_config.model.name,
|
28
|
-
instruction=agent_config.instruction,
|
28
|
+
name=agent_config.metadata.name,
|
29
|
+
model=agent_config.agent.model.name,
|
30
|
+
instruction=agent_config.agent.instruction,
|
29
31
|
tools=tools,
|
30
32
|
)
|
31
33
|
|
32
34
|
@staticmethod
|
33
|
-
def build_agent_card(agent_config:
|
35
|
+
def build_agent_card(agent_config: AigencyConfig) -> AgentCard:
|
34
36
|
|
35
37
|
# TODO: Parse properly
|
36
|
-
capabilities = AgentCapabilities(
|
38
|
+
capabilities = AgentCapabilities(
|
39
|
+
streaming=agent_config.service.capabilities.streaming
|
40
|
+
)
|
37
41
|
|
38
42
|
skills = [
|
39
43
|
AgentSkill(
|
@@ -43,24 +47,22 @@ class AgentA2AGenerator:
|
|
43
47
|
tags=skill.tags,
|
44
48
|
examples=skill.examples,
|
45
49
|
)
|
46
|
-
for skill in agent_config.skills
|
50
|
+
for skill in agent_config.agent.skills
|
47
51
|
]
|
48
52
|
|
49
53
|
return AgentCard(
|
50
|
-
name=agent_config.name,
|
51
|
-
description=agent_config.description,
|
52
|
-
url=agent_config.url,
|
53
|
-
version=agent_config.version,
|
54
|
-
default_input_modes=agent_config.default_input_modes,
|
55
|
-
default_output_modes=agent_config.default_output_modes,
|
54
|
+
name=agent_config.metadata.name,
|
55
|
+
description=agent_config.metadata.description,
|
56
|
+
url=agent_config.service.url,
|
57
|
+
version=agent_config.metadata.version,
|
58
|
+
default_input_modes=agent_config.service.interface.default_input_modes,
|
59
|
+
default_output_modes=agent_config.service.interface.default_output_modes,
|
56
60
|
capabilities=capabilities,
|
57
61
|
skills=skills,
|
58
62
|
)
|
59
63
|
|
60
64
|
@staticmethod
|
61
|
-
def build_executor(
|
62
|
-
agent: Agent, agent_card: AgentCard
|
63
|
-
) -> AgentA2AExecutor:
|
65
|
+
def build_executor(agent: Agent, agent_card: AgentCard) -> AgentA2AExecutor:
|
64
66
|
|
65
67
|
runner = Runner(
|
66
68
|
app_name=agent.name,
|
@@ -0,0 +1,12 @@
|
|
1
|
+
from pydantic import BaseModel
|
2
|
+
from typing import List, Optional
|
3
|
+
from aigency.schemas.agent.model import AgentModel
|
4
|
+
from aigency.schemas.agent.skills import Skill
|
5
|
+
from aigency.schemas.agent.tools import FunctionTool, McpTool
|
6
|
+
|
7
|
+
class Agent(BaseModel):
|
8
|
+
"""El 'cerebro' del agente: su lógica, modelo y capacidades."""
|
9
|
+
model: AgentModel
|
10
|
+
instruction: str
|
11
|
+
skills: List[Skill]
|
12
|
+
tools: Optional[List[FunctionTool | McpTool]] = []
|
@@ -0,0 +1,12 @@
|
|
1
|
+
from typing import Optional
|
2
|
+
from pydantic import BaseModel
|
3
|
+
|
4
|
+
class ProviderConfig(BaseModel):
|
5
|
+
"""Configuration for AI model provider."""
|
6
|
+
name: str
|
7
|
+
endpoint: Optional[str] = None
|
8
|
+
|
9
|
+
class AgentModel(BaseModel):
|
10
|
+
"""Configuration for AI model."""
|
11
|
+
name: str
|
12
|
+
provider: Optional[ProviderConfig] = None
|
@@ -0,0 +1,14 @@
|
|
1
|
+
from pydantic import BaseModel
|
2
|
+
from typing import Optional
|
3
|
+
from aigency.schemas.observability.observability import Observability
|
4
|
+
from aigency.schemas.metadata.metadata import Metadata
|
5
|
+
from aigency.schemas.agent.agent import Agent
|
6
|
+
from aigency.schemas.service.service import Service
|
7
|
+
|
8
|
+
class AigencyConfig(BaseModel):
|
9
|
+
"""Root Pydantic model for complete agent configuration."""
|
10
|
+
|
11
|
+
metadata: Metadata
|
12
|
+
service: Service
|
13
|
+
agent: Agent
|
14
|
+
observability: Optional[Observability] = None
|
@@ -0,0 +1,10 @@
|
|
1
|
+
from pydantic import BaseModel
|
2
|
+
from aigency.schemas.observability.phoenix import Phoenix
|
3
|
+
|
4
|
+
class Monitoring(BaseModel):
|
5
|
+
"""Configuración de las herramientas de monitoreo."""
|
6
|
+
phoenix: Phoenix
|
7
|
+
|
8
|
+
class Observability(BaseModel):
|
9
|
+
"""Agrupa todas las configuraciones de observabilidad."""
|
10
|
+
monitoring: Monitoring
|