Promotion
CogSol tenants are organized across separate environments: a development environment, where agents are configured, adjusted, and where bugs are fixed, and a production environment, which serves real users.
Promotion is the process of moving the configuration built in one environment to the next one, so changes made and validated in development become available in production.
Promotion is managed from the Deploy section of the development tenant's portal, which offers two options:
- Tenant: promotes all the data of a module (content or cognitive) of the tenant.
- Agent: promotes a single agent together with everything it needs.
Only users with the admin role can access the Deploy section.
Tenant promotion
Promotion Types
There are two independent promotion types:
- Content: promotes the content-related configuration (e.g., topics, documents, metadata configs).
- Cognitive: promotes the agent-related configuration (e.g., agents, tools, flows).
Implementers are encouraged to always run both promotion types, one after the other, so content and agent configurations stay in sync between environments.
Running a Promotion
Tenant promotion is managed from Deploy > Tenant.
- Review the Tenant details panel, which shows the current tenant and the destination environment the promotion will target.
- Under Module, select which promotion type to run: Content or Cognitive.
- Click Start promotion to begin the promotion.
Promotion Run History
The Recent promotion runs table shows the last 10 promotion runs for the tenant, with:
- Run ID
- Start Date
- End Date
- Status
This history lets you confirm whether a promotion completed successfully and when it ran, without needing to start a new one.
Agent promotion
Agent promotion moves one agent and everything it needs (tools, MCP tools, searches, topics, documents, citation styles, metadata configs, model configurations and other dependencies) to the next configured environment. It is useful when you want to publish the changes of a single agent without promoting the whole tenant.
Agent promotion is managed from Deploy > Agent. The source is the tenant currently selected in the portal, and the target is the next configured environment; both are shown at the top of the page. If no target environment is configured, the promotion cannot be run.
Step 1: Analyze the agent
- In Agent to Promote, search for and select the agent. Only enabled agents are listed.
- Click Analyze.
Analyzing is read-only: it writes nothing to any environment and can be repeated as many times as you want. Each new analysis replaces the previous one for the same agent.
Step 2: Review the transfer plan
The Transfer Plan indicates whether the agent already exists in the target environment or will be created, and lists each object involved, grouped under Cognitive, Content and Generator, with the action that will be applied to it:
| Action | Meaning |
|---|---|
| Create | The object does not exist in the target and will be created. |
| Update | The object exists in the target and will be updated. |
| Unchanged | The object is already identical in the target. |
| Reuse on target | The existing object in the target will be used. |
| Absent | The object is not present, so no action is applied to it. |
The agent's dependencies are resolved automatically: everything it needs travels with it.
Decisions
When an object already exists or is shared in the target, the plan may include Decisions, for example whether to keep the target's version, bring the source's version, or overwrite it. Each decision is marked as:
- Optional: it comes resolved with a default choice, which you can change.
- Decision required: you must choose an option before running the transfer.
- Resolved: a required decision that has already been answered.
- Hard block: the conflict cannot be resolved, and the transfer cannot be run.
Warnings
The plan may also include Warnings, such as notices about resources shared with other agents. They are informational and do not block the transfer.
Step 3: Run the transfer
The Review panel summarizes the route, the agent, the number of objects to create or update and the decisions resolved. Once the plan has been reviewed and all required decisions are resolved, click Run the Transfer. This writes to the target environment.
Do not close the screen while the transfer is running. The result can be:
- Applied: the agent and its dependencies are now in the target environment.
- Partial: part of the plan was written to the target. Analyze again and run the transfer to complete it; what was already applied is not overwritten.
- Failed: nothing was applied. Analyze again to retry.
If something changes in the source or target environment after the analysis, the plan becomes stale and can no longer be run. Analyze again to build a new plan.