What are the trigger conditions for the self-upgrade, and how do you manage MCP connections and permissions during an update? Also, what’s your strategy for rollbacks?
Connections and MCP connections (these are different) credentials are saved on the Airlock's (platform's) side. So the credentials are kept after an agent upgrade. Permissions are defined in the agent's code (admin/user/public) and are auto-updated.
Rollbacks are not possible right now. But every agent's update is a git commit. And every agent has to write migrations. In the near future an option to rollback to a specific build will be added. Right now I think you can try to just request an upgrade to rollback, I think the builder agent will be able to look into git history and rollback. But this is not really tested.
As I mentioned before this is an alpha version.