Skip to content
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(r3corda): enable DLT deployment via GitHub Workflow & Action. #2499

Merged

Conversation

sailajakommineni
Copy link
Contributor

Changes:
Introduced a new GitHub Workflow enabling the deployment of Hyperledger Bevel's CORDA DLT Platform to an EKS Cluster. Introduced a new directory at path: platforms/r3-corda/configuration/samples/workflow, containing two new sample network configuration files: network-proxy-corda: Supports deployment with Ingress controller. network-no-proxy-corda: Supports deployment without an Ingress controller, specifically designed for deployment on Minikube.

Additional Changes:
Allowing to choose between the 'deploy' and 'reset' actions when manually triggering it through the GitHub Actions UI.

fixes #2416

Changes:
Introduced a new GitHub Workflow enabling the deployment of Hyperledger Bevel's CORDA DLT Platform to an EKS Cluster.
Introduced a new directory at path: platforms/r3-corda/configuration/samples/workflow, containing two new sample network configuration files:
network-proxy-corda: Supports deployment with Ingress controller.
network-no-proxy-corda: Supports deployment without an Ingress controller, specifically designed for deployment on Minikube.

Additional Changes:

Allowing to choose between the 'deploy' and 'reset' actions when manually triggering it through the GitHub Actions UI.

fixes hyperledger-bevel#2416

Signed-off-by: sailajakommineni <[email protected]>
@suvajit-sarkar suvajit-sarkar merged commit 5025d9d into hyperledger-bevel:develop Feb 6, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants