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
This guide explains how to publish ABI agents as remote plugins on the Naas platform. This feature is only available if you have access to the Naas platform.
4
4
5
+
## Automatic Publishing (Recommended)
6
+
7
+
The system now supports automatic publishing of remote agents to your workspace. When enabled, agents will be automatically published to the specified workspace using `config.workspace_id` whenever the API is deployed.
8
+
5
9
## Prerequisites
6
10
7
11
Before publishing remote agents, ensure you have:
@@ -32,32 +36,79 @@ Update your `config.yaml` file with the following settings:
32
36
```yaml
33
37
config:
34
38
workspace_id: "your_naas_workspace_id"
39
+
auto_publish:
40
+
enabled: true # Enable automatic publishing of agents to workspace
41
+
exclude_agents: [] # Agents to exclude from auto-publishing (empty list means publish all enabled agents)
42
+
default_agent: "Abi"# Which agent to set as default in workspace
|`exclude_agents`| List of agent names to exclude from publishing |`[]`|`["TestAgent", "DebugAgent"]`|
54
+
|`default_agent`| Agent to set as default in the workspace |`"Abi"`|`"MyCustomAgent"`|
55
+
40
56
## How to Publish Remote Agents
41
57
42
-
### Method 1: Using Make Command (Recommended)
58
+
### Method 1: Automatic Publishing (Recommended)
59
+
60
+
When `auto_publish.enabled` is set to `true` in your `config.yaml`, agents will be automatically published to your workspace after each API deployment via GitHub Actions.
43
61
44
-
The easiest way to publish remote agents is using the provided Make command:
62
+
**Benefits:**
63
+
- ✅ Simplifies deployment workflow
64
+
- ✅ Ensures agents are up-to-date
65
+
- ✅ Reduces manual intervention
66
+
- ✅ Publishes all enabled agents automatically
67
+
- ✅ Excludes only specified agents via `exclude_agents`
68
+
69
+
**How it works:**
70
+
1. GitHub Actions workflow triggers after successful API deployment
71
+
2. Checks if auto-publish is enabled in configuration
72
+
3. Verifies API accessibility
73
+
4. Publishes all enabled agents except those in `exclude_agents`
74
+
5. Sets the `default_agent` as the workspace default
75
+
76
+
### Method 2: Manual Publishing with Make Command
77
+
78
+
You can also manually publish agents using:
45
79
46
80
```bash
47
81
make publish-remote-agents
48
82
```
49
-
This command performs the following actions:
50
-
1. Reads configuration settings from your environment and config files
51
-
2. Publishes a predefined set of agents:
52
-
-`Abi` (set as default)
53
-
-`Ontology`
54
-
-`Naas`
55
-
-`Multi_Models`
56
-
-`Support`
57
-
3. Configures the published agents with appropriate settings
58
-
59
-
To customize which agents are published, you can modify the `agents_to_publish` list directly in the script.
60
-
Use the agent name to add more agents to publish.
83
+
84
+
**Dry-Run Mode (Preview Changes):**
85
+
To preview what agents would be published without making actual changes:
86
+
87
+
```bash
88
+
make publish-remote-agents-dry-run
89
+
```
90
+
91
+
Or directly:
92
+
```bash
93
+
uv run python scripts/publish_remote_agents.py --dry-run
0 commit comments