Upgrades¶

AgentCube connectors are upgraded by deploying a new container image version.

Upgrade Procedure¶

1. Check the New Version¶

Review the release notes for the new version to understand what has changed.

2. Pull and Deploy the New Image¶

Update your container deployment to use the new image version:

# Azure Container Apps example
az containerapp update \
  --name {app_name} \
  --resource-group {resource_group} \
  --image ghcr.io/caprusai/agentcube-essbase:{new_version} \
  --revision-suffix "v{new_version}"

Unique revision suffix

Always include a unique --revision-suffix when deploying to Azure Container Apps. This ensures the platform pulls the new image rather than using a cached version.

3. Verify the Upgrade¶

curl https://{connector_hostname}/health

Confirm:

version matches the new version
status is healthy
backend_connected is true (basic mode) or null (OIDC mode)

4. Test a Tool Call¶

From your AI platform, run a tool call (e.g., list_applications) to verify end-to-end functionality.

Version Numbering¶

Essbase and Planning connectors are versioned independently using semantic versioning:

Format	Example
Essbase	`essbase-v{major}.{minor}.{patch}`
Planning	`planning-v{major}.{minor}.{patch}`

The SDK version is embedded in each connector image and reported in the health endpoint.

Rollback¶

If the upgrade causes issues, see Rollbacks to revert to the previous version.

AI Platform Notes¶

Copilot Studio tool cache

After upgrading a connector, Copilot Studio may cache stale tool definitions. Disconnect and reconnect the MCP connector in your agent's Actions settings to refresh.

Claude.ai automatically picks up tool definition changes on the next conversation.