[WIP] Implement Introduce API in basic controller

libs/aries-basic-controller/aries_basic_controller/controllers/connections.py

@@ -175,3 +175,16 @@ async def is_active(self, connection_id):
             logger.error(f"Connection {connection_id} not active")
             raise Exception("Connection must be active to send a credential")
         return
+
+    async def propose_introduction(
+        self,
+        connection_id: str,
+        target_connection_id: str,
+        message: str
+    ):
+        params = {
+            "target_connection_id": target_connection_id
+        }
+        if message:
+            params["message"] = message
+        return await self.admin_POST(f"/connections/{connection_id}/start-introduction", params=params)

tutorials/aries-basic-controller/notebooks/alice/Part 2 - Aries Basic Controller.ipynb

@@ -6,7 +6,7 @@
    "source": [
     "# Aries Basic Controller\n",
     "\n",
-    "The aries basic controller is a simple python library that wraps a swagger api exposed by the BCGov [ACA-Py Agent implementation](https://github.com/hyperledger/aries-cloudagent-python). It is designed to enable easy, programatic interface between business logic of an application (this is what you will write) and the capabilities of the Hyperledger SSI stack currently implemented by this agent codebase, such as the issue-credential protocol. These are all defined in [aries-rfcs](https://github.com/hyperledger/aries-rfcs)."
+    "The aries basic controller is a simple python library that wraps a swagger api exposed by the BCGov [ACA-Py Agent implementation](https://github.com/hyperledger/aries-cloudagent-python). It is designed to enable easy, programmatic interface between business logic of an application (this is what you will write) and the capabilities of the Hyperledger SSI stack currently implemented by this agent codebase, such as the issue-credential protocol. These are all defined in [aries-rfcs](https://github.com/hyperledger/aries-rfcs)."
    ]
   },
   {
@@ -30,7 +30,7 @@
     "\n",
     "The components of an SSI application that uses ACA-Py are:\n",
     "\n",
-    "* The business/application logic - This is up to you and your imagination. What credentials does your application issue, what proofs do they expect to verify and what happens once a proof has been successfully verified? It can be as simple of complicated as you want.\n",
+    "* The business/application logic - This is up to you and your imagination. What credentials does your application issue, what proofs do they expect to verify and what happens once a proof has been successfully verified? It can be as simple or complicated as you want.\n",
     "* A controller - The aries-basic-contoller is an example of this, but it could be written in any language. It is the mechansism for the business logic to invoke aries protocols. E.g. write this credential schema to the ledger for me, or issue this connection this credential with these attributes.\n",
     "* An SSI agent - The implementations of a set of specified aries-rfcs, not all agents have the same set implemented. The agent code interfaces with a ledger, manages a wallet and interacts with other agents.\n",
     "\n",

tutorials/aries-basic-controller/notebooks/alice/Part 3 - Establishing a Connection.ipynb

@@ -70,7 +70,7 @@
     }
    },
    "source": [
-    "### 2. Instatiate the controller for our Agent\n",
+    "### 2. Instantiate the controller for our Agent\n",
     "\n",
     "The arguments depend on how the aca-py agent was initiated. See the manage and docker-compose.yml files for more details."
    ]

tutorials/aries-basic-controller/notebooks/bob/Part 3 - Establishing a Connection.ipynb

@@ -36,7 +36,7 @@
     }
    },
    "source": [
-    "### 6. Instatiate the controller for our Agent"
+    "### 6. Instantiate the controller for our Agent"
    ]
   },
   {