You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: implement auto-dependency resolution for resource pushing
- Added functionality to automatically resolve and apply missing dependencies when pushing squads and assistants, enhancing the deployment process.
- Introduced new methods to ensure the existence of tools, structured outputs, and assistants, streamlining the resource management workflow.
- Updated the README to document the new auto-dependency resolution feature and its usage, providing clear guidance for users on selective pushes.
Copy file name to clipboardExpand all lines: README.md
+32Lines changed: 32 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -161,6 +161,38 @@ npm run push:dev assistants resources/assistants/booking.md
161
161
162
162
**Note:** Partial pushes skip deletion checks. Run full `npm run push:dev` to sync deletions.
163
163
164
+
#### Auto-Dependency Resolution
165
+
166
+
Partial push is ideal for promoting specific squads or assistants to staging/prod without pushing everything. The engine automatically detects and creates missing dependencies:
167
+
168
+
```bash
169
+
# Push a single squad to staging — tools, structured outputs, and
170
+
# assistants are created automatically if they don't exist yet
171
+
npm run push:stg resources/squads/everblue-voice-squad-20374c37.yml
172
+
173
+
# Push assistants to prod — missing tools and structured outputs
174
+
# are auto-applied first so references resolve correctly
175
+
npm run push:prod assistants
176
+
```
177
+
178
+
The dependency chain resolves recursively:
179
+
180
+
```
181
+
Squad push
182
+
└─ missing assistants? → auto-create them first
183
+
└─ missing tools / structured outputs? → auto-create those first
184
+
└─ then create the assistant
185
+
└─ all references resolved → create the squad ✓
186
+
187
+
Assistant push
188
+
└─ missing tools / structured outputs? → auto-create them first
189
+
└─ all references resolved → create the assistant ✓
190
+
```
191
+
192
+
If a dependency already exists on the platform (UUID in the state file) but its nested dependencies don't, those are still auto-created and the parent resource is updated to reference them.
193
+
194
+
This means you can work on everything in dev, then selectively push a single squad or assistant to staging or prod — no need for a full `push` that touches every resource.
0 commit comments