-
Notifications
You must be signed in to change notification settings - Fork 285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(connector-corda): containerize plugin #789
Comments
I will continue this issue! |
@elenaizaguirre Are you still working on this? And if yes, are you working directly on Jordi's old branch (#805) or did you start a new one? |
@petermetz Sorry, I completely forgot this issue. I can work on it when I finish the one I'm working on. |
@elenaizaguirre No worries, it's easy to lose track. Recently, I've been using the VSCode GitHub extension to keep track of assigned issues/old PRs and it's been much easier through that compared to the web UI so I recommend you give it a try too if you are interested. |
Allow plugin-ledger-connector-corda to read privateKey from filesystem instead of obtain it directly from corda-aiio container Relationed with hyperledger-cacti#789 Signed-off-by: Elena Izaguirre <e.izaguirre.equiza@accenture.com>
Allow plugin-ledger-connector-corda to read privateKey from filesystem instead of obtain it directly from corda-aiio container Relationed with hyperledger-cacti#789 Signed-off-by: Elena Izaguirre <e.izaguirre.equiza@accenture.com>
Allow plugin-ledger-connector-corda to read privateKey from filesystem instead of obtain it directly from corda-aiio container Relationed with hyperledger-cacti#789 Signed-off-by: Elena Izaguirre <e.izaguirre.equiza@accenture.com>
Allow plugin-ledger-connector-corda to read privateKey from filesystem instead of obtain it directly from corda-aiio container Relationed with hyperledger-cacti#789 Signed-off-by: Elena Izaguirre <e.izaguirre.equiza@accenture.com>
Allow plugin-ledger-connector-corda to read privateKey from filesystem instead of obtain it directly from corda-aiio container Relationed with hyperledger-cacti#789 Signed-off-by: Elena Izaguirre <e.izaguirre.equiza@accenture.com>
Allow plugin-ledger-connector-corda to read privateKey from filesystem instead of obtain it directly from corda-aiio container Relationed with #789 Signed-off-by: Elena Izaguirre <e.izaguirre.equiza@accenture.com>
Allow plugin-ledger-connector-corda to read privateKey from filesystem instead of obtain it directly from corda-aiio container Relationed with hyperledger-cacti#789 Signed-off-by: Elena Izaguirre <e.izaguirre.equiza@accenture.com> Signed-off-by: aldousalvarez <aldousss.alvarez@gmail.com>
Allow plugin-ledger-connector-corda to read privateKey from filesystem instead of obtain it directly from corda-aiio container Relationed with hyperledger-cacti#789 Signed-off-by: Elena Izaguirre <e.izaguirre.equiza@accenture.com> Signed-off-by: aldousalvarez <aldousss.alvarez@gmail.com>
Closing this down for now because it's for Corda v4 but we are focusing on Corda v5. |
Is your feature request related to a problem? Please describe.
Cloud has became the de-facto way of running applications on computers.
Containers are rapidly becoming (have become?) the de-facto way of running applications in the cloud.
We therefore need to make sure that Cactus is not just built and distributed as the language native artifacts (e.g. npm packages/webpack bundles) but that it's also distributed as containers.
This doesn't just mean containerizing the API server that can host the plugins, but also means containerizing each plugin individually as well OR providing a generic image of the API server that can be configured to run any and all of the available Cactus plugins on-demand.
Describe the solution you'd like
I want to be able to whisper things like this to my terminal and expect to have a fully functional connector for Ledger X up and running in a few seconds and with the config.json file mounted at the specified path/volume that gets picked up by the API server running inside the container as well.
Acceptance criteria
The text was updated successfully, but these errors were encountered: