...

...

For additional information, one can check out the current usage of plugins within the api-server docs

Milestones

(Each milestone is set to be achieved in 2 weeks time)

•  Understand the current objective to be completed for fabric and vault connector
•  Update vault connector to have an optional field which enables reading of root token via environment variable
•  Run the vault connector for a production grade vault deployment (vault residing over a EC2 machine or as a kubernetes pod), and identify further gaps in the connector, if any
•  Fix the gaps by introducing additional optional fields in the vault connector
•  Update vault test cases and the example codes using vault connector
•  Update fabric connector to have pluginRegistry as an optional field (if its optional, during its initialisation while fabric connector is getting started, the pluginRegistry keychainID to be printed in plugin initialization logs)
•  Run the fabric connector for a production grade fabric network (setup via Bevel) and see for further gaps, if any
•  Fix the gaps by introducing additional optional fields in the fabric connector
•  Update the fabric connector to have an optional field which enables the reading of connectionProfile from environment variable, same for the sshConfig variable
•  Update the test cases and sample examples to have these fields if required (the above changes should be done in such a manner that it doesn't disrupt the test cases & example code by a lot)
•  Create a single PR to the Cacti codebase to address all the above done changes
•  Create the final presentation/demo to showcase the work done

Learning Objectives

Through this, the mentee can learn production grade best practices along with the usage and creation of Hyperledger Cacti plugins and their interaction with the api-server

...