-
Notifications
You must be signed in to change notification settings - Fork 286
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
fix(besu): deployContractSolBytecodeNoKeychainV1 requires keychainId #3586
Comments
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Oct 14, 2024
In the DeployContractSolidityBytecodeNoKeychainV1Request of `packages/cactus-plugin-ledger-connector-besu/src/main/json/openapi.tpl.json` there are parameters that are required despite the entire point of this operation is to not need them (e.g. keychainId and contract JSON object). Fixes hyperledger-cacti#3586 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
5 tasks
brunoffmateus
pushed a commit
to brunoffmateus/blockchain-integration-framework
that referenced
this issue
Oct 15, 2024
In the DeployContractSolidityBytecodeNoKeychainV1Request of `packages/cactus-plugin-ledger-connector-besu/src/main/json/openapi.tpl.json` there are parameters that are required despite the entire point of this operation is to not need them (e.g. keychainId and contract JSON object). Fixes hyperledger-cacti#3586 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Oct 17, 2024
In the DeployContractSolidityBytecodeNoKeychainV1Request of `packages/cactus-plugin-ledger-connector-besu/src/main/json/openapi.tpl.json` there are parameters that are required despite the entire point of this operation is to not need them (e.g. keychainId and contract JSON object). Fixes hyperledger-cacti#3586 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
brunoffmateus
added a commit
to brunoffmateus/blockchain-integration-framework
that referenced
this issue
Oct 18, 2024
Signed-off-by: Bruno Mateus <brumat315@gmail.com> refactor(satp-hermes): gateway container image definition with bundler Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): merge policies type guard example Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): type guards for SATP env variables Signed-off-by: Bruno Mateus <brumat315@gmail.com> squash! - peter's fixes for besu connectivity use LAN IP Instead of hardcoded localhost use the LAN IP of machine so that the gateway container can access it too. Why though? Because if you tell the gateway container that it should access the besu ledger via localhost then it will try to do that through the container's own localhost, which is different from the host machine's localhost (where the besu ledger is actually running). Using the actual IP address of the host machine's primary network interface resolves the ambiguity between the two differnet localhosts. Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> fix(besu): deployContractSolBytecodeNoKeychainV1 requires keychainId In the DeployContractSolidityBytecodeNoKeychainV1Request of `packages/cactus-plugin-ledger-connector-besu/src/main/json/openapi.tpl.json` there are parameters that are required despite the entire point of this operation is to not need them (e.g. keychainId and contract JSON object). Fixes hyperledger-cacti#3586 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
brunoffmateus
added a commit
to brunoffmateus/blockchain-integration-framework
that referenced
this issue
Oct 18, 2024
Signed-off-by: Bruno Mateus <brumat315@gmail.com> refactor(satp-hermes): gateway container image definition with bundler Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): merge policies type guard example Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): type guards for SATP env variables Signed-off-by: Bruno Mateus <brumat315@gmail.com> squash! - peter's fixes for besu connectivity use LAN IP Instead of hardcoded localhost use the LAN IP of machine so that the gateway container can access it too. Why though? Because if you tell the gateway container that it should access the besu ledger via localhost then it will try to do that through the container's own localhost, which is different from the host machine's localhost (where the besu ledger is actually running). Using the actual IP address of the host machine's primary network interface resolves the ambiguity between the two differnet localhosts. Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> fix(besu): deployContractSolBytecodeNoKeychainV1 requires keychainId In the DeployContractSolidityBytecodeNoKeychainV1Request of `packages/cactus-plugin-ledger-connector-besu/src/main/json/openapi.tpl.json` there are parameters that are required despite the entire point of this operation is to not need them (e.g. keychainId and contract JSON object). Fixes hyperledger-cacti#3586 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
brunoffmateus
added a commit
to brunoffmateus/blockchain-integration-framework
that referenced
this issue
Oct 23, 2024
Signed-off-by: Bruno Mateus <brumat315@gmail.com> refactor(satp-hermes): gateway container image definition with bundler Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): merge policies type guard example Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): type guards for SATP env variables Signed-off-by: Bruno Mateus <brumat315@gmail.com> squash! - peter's fixes for besu connectivity use LAN IP Instead of hardcoded localhost use the LAN IP of machine so that the gateway container can access it too. Why though? Because if you tell the gateway container that it should access the besu ledger via localhost then it will try to do that through the container's own localhost, which is different from the host machine's localhost (where the besu ledger is actually running). Using the actual IP address of the host machine's primary network interface resolves the ambiguity between the two differnet localhosts. Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> fix(besu): deployContractSolBytecodeNoKeychainV1 requires keychainId In the DeployContractSolidityBytecodeNoKeychainV1Request of `packages/cactus-plugin-ledger-connector-besu/src/main/json/openapi.tpl.json` there are parameters that are required despite the entire point of this operation is to not need them (e.g. keychainId and contract JSON object). Fixes hyperledger-cacti#3586 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
brunoffmateus
added a commit
to brunoffmateus/blockchain-integration-framework
that referenced
this issue
Oct 24, 2024
Signed-off-by: Bruno Mateus <brumat315@gmail.com> refactor(satp-hermes): gateway container image definition with bundler Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): merge policies type guard example Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): type guards for SATP env variables Signed-off-by: Bruno Mateus <brumat315@gmail.com> squash! - peter's fixes for besu connectivity use LAN IP Instead of hardcoded localhost use the LAN IP of machine so that the gateway container can access it too. Why though? Because if you tell the gateway container that it should access the besu ledger via localhost then it will try to do that through the container's own localhost, which is different from the host machine's localhost (where the besu ledger is actually running). Using the actual IP address of the host machine's primary network interface resolves the ambiguity between the two differnet localhosts. Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> fix(besu): deployContractSolBytecodeNoKeychainV1 requires keychainId In the DeployContractSolidityBytecodeNoKeychainV1Request of `packages/cactus-plugin-ledger-connector-besu/src/main/json/openapi.tpl.json` there are parameters that are required despite the entire point of this operation is to not need them (e.g. keychainId and contract JSON object). Fixes hyperledger-cacti#3586 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
brunoffmateus
added a commit
to brunoffmateus/blockchain-integration-framework
that referenced
this issue
Oct 24, 2024
Signed-off-by: Bruno Mateus <brumat315@gmail.com> refactor(satp-hermes): gateway container image definition with bundler Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): merge policies type guard example Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): type guards for SATP env variables Signed-off-by: Bruno Mateus <brumat315@gmail.com> squash! - peter's fixes for besu connectivity use LAN IP Instead of hardcoded localhost use the LAN IP of machine so that the gateway container can access it too. Why though? Because if you tell the gateway container that it should access the besu ledger via localhost then it will try to do that through the container's own localhost, which is different from the host machine's localhost (where the besu ledger is actually running). Using the actual IP address of the host machine's primary network interface resolves the ambiguity between the two differnet localhosts. Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> fix(besu): deployContractSolBytecodeNoKeychainV1 requires keychainId In the DeployContractSolidityBytecodeNoKeychainV1Request of `packages/cactus-plugin-ledger-connector-besu/src/main/json/openapi.tpl.json` there are parameters that are required despite the entire point of this operation is to not need them (e.g. keychainId and contract JSON object). Fixes hyperledger-cacti#3586 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
brunoffmateus
added a commit
to brunoffmateus/blockchain-integration-framework
that referenced
this issue
Oct 24, 2024
Signed-off-by: Bruno Mateus <brumat315@gmail.com> refactor(satp-hermes): gateway container image definition with bundler Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): merge policies type guard example Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): type guards for SATP env variables Signed-off-by: Bruno Mateus <brumat315@gmail.com> squash! - peter's fixes for besu connectivity use LAN IP Instead of hardcoded localhost use the LAN IP of machine so that the gateway container can access it too. Why though? Because if you tell the gateway container that it should access the besu ledger via localhost then it will try to do that through the container's own localhost, which is different from the host machine's localhost (where the besu ledger is actually running). Using the actual IP address of the host machine's primary network interface resolves the ambiguity between the two differnet localhosts. Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> fix(besu): deployContractSolBytecodeNoKeychainV1 requires keychainId In the DeployContractSolidityBytecodeNoKeychainV1Request of `packages/cactus-plugin-ledger-connector-besu/src/main/json/openapi.tpl.json` there are parameters that are required despite the entire point of this operation is to not need them (e.g. keychainId and contract JSON object). Fixes hyperledger-cacti#3586 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
brunoffmateus
added a commit
to brunoffmateus/blockchain-integration-framework
that referenced
this issue
Oct 24, 2024
Signed-off-by: Bruno Mateus <brumat315@gmail.com> refactor(satp-hermes): gateway container image definition with bundler Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): merge policies type guard example Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): type guards for SATP env variables Signed-off-by: Bruno Mateus <brumat315@gmail.com> squash! - peter's fixes for besu connectivity use LAN IP Instead of hardcoded localhost use the LAN IP of machine so that the gateway container can access it too. Why though? Because if you tell the gateway container that it should access the besu ledger via localhost then it will try to do that through the container's own localhost, which is different from the host machine's localhost (where the besu ledger is actually running). Using the actual IP address of the host machine's primary network interface resolves the ambiguity between the two differnet localhosts. Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> fix(besu): deployContractSolBytecodeNoKeychainV1 requires keychainId In the DeployContractSolidityBytecodeNoKeychainV1Request of `packages/cactus-plugin-ledger-connector-besu/src/main/json/openapi.tpl.json` there are parameters that are required despite the entire point of this operation is to not need them (e.g. keychainId and contract JSON object). Fixes hyperledger-cacti#3586 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
brunoffmateus
added a commit
to brunoffmateus/blockchain-integration-framework
that referenced
this issue
Oct 24, 2024
Signed-off-by: Bruno Mateus <brumat315@gmail.com> refactor(satp-hermes): gateway container image definition with bundler Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): merge policies type guard example Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): type guards for SATP env variables Signed-off-by: Bruno Mateus <brumat315@gmail.com> squash! - peter's fixes for besu connectivity use LAN IP Instead of hardcoded localhost use the LAN IP of machine so that the gateway container can access it too. Why though? Because if you tell the gateway container that it should access the besu ledger via localhost then it will try to do that through the container's own localhost, which is different from the host machine's localhost (where the besu ledger is actually running). Using the actual IP address of the host machine's primary network interface resolves the ambiguity between the two differnet localhosts. Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> fix(besu): deployContractSolBytecodeNoKeychainV1 requires keychainId In the DeployContractSolidityBytecodeNoKeychainV1Request of `packages/cactus-plugin-ledger-connector-besu/src/main/json/openapi.tpl.json` there are parameters that are required despite the entire point of this operation is to not need them (e.g. keychainId and contract JSON object). Fixes hyperledger-cacti#3586 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
brunoffmateus
added a commit
to brunoffmateus/blockchain-integration-framework
that referenced
this issue
Oct 24, 2024
Signed-off-by: Bruno Mateus <brumat315@gmail.com> refactor(satp-hermes): gateway container image definition with bundler Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): merge policies type guard example Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): type guards for SATP env variables Signed-off-by: Bruno Mateus <brumat315@gmail.com> squash! - peter's fixes for besu connectivity use LAN IP Instead of hardcoded localhost use the LAN IP of machine so that the gateway container can access it too. Why though? Because if you tell the gateway container that it should access the besu ledger via localhost then it will try to do that through the container's own localhost, which is different from the host machine's localhost (where the besu ledger is actually running). Using the actual IP address of the host machine's primary network interface resolves the ambiguity between the two differnet localhosts. Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> fix(besu): deployContractSolBytecodeNoKeychainV1 requires keychainId In the DeployContractSolidityBytecodeNoKeychainV1Request of `packages/cactus-plugin-ledger-connector-besu/src/main/json/openapi.tpl.json` there are parameters that are required despite the entire point of this operation is to not need them (e.g. keychainId and contract JSON object). Fixes hyperledger-cacti#3586 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> Co-authored-by: Peter Somogyvari <peter.somogyvari@accenture.com>
brunoffmateus
added a commit
to brunoffmateus/blockchain-integration-framework
that referenced
this issue
Oct 28, 2024
Signed-off-by: Bruno Mateus <brumat315@gmail.com> refactor(satp-hermes): gateway container image definition with bundler Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): merge policies type guard example Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): type guards for SATP env variables Signed-off-by: Bruno Mateus <brumat315@gmail.com> squash! - peter's fixes for besu connectivity use LAN IP Instead of hardcoded localhost use the LAN IP of machine so that the gateway container can access it too. Why though? Because if you tell the gateway container that it should access the besu ledger via localhost then it will try to do that through the container's own localhost, which is different from the host machine's localhost (where the besu ledger is actually running). Using the actual IP address of the host machine's primary network interface resolves the ambiguity between the two differnet localhosts. Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> fix(besu): deployContractSolBytecodeNoKeychainV1 requires keychainId In the DeployContractSolidityBytecodeNoKeychainV1Request of `packages/cactus-plugin-ledger-connector-besu/src/main/json/openapi.tpl.json` there are parameters that are required despite the entire point of this operation is to not need them (e.g. keychainId and contract JSON object). Fixes hyperledger-cacti#3586 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> Co-authored-by: Peter Somogyvari <peter.somogyvari@accenture.com>
brunoffmateus
added a commit
to brunoffmateus/blockchain-integration-framework
that referenced
this issue
Oct 28, 2024
Signed-off-by: Bruno Mateus <brumat315@gmail.com> refactor(satp-hermes): gateway container image definition with bundler Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): merge policies type guard example Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): type guards for SATP env variables Signed-off-by: Bruno Mateus <brumat315@gmail.com> squash! - peter's fixes for besu connectivity use LAN IP Instead of hardcoded localhost use the LAN IP of machine so that the gateway container can access it too. Why though? Because if you tell the gateway container that it should access the besu ledger via localhost then it will try to do that through the container's own localhost, which is different from the host machine's localhost (where the besu ledger is actually running). Using the actual IP address of the host machine's primary network interface resolves the ambiguity between the two differnet localhosts. Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> fix(besu): deployContractSolBytecodeNoKeychainV1 requires keychainId In the DeployContractSolidityBytecodeNoKeychainV1Request of `packages/cactus-plugin-ledger-connector-besu/src/main/json/openapi.tpl.json` there are parameters that are required despite the entire point of this operation is to not need them (e.g. keychainId and contract JSON object). Fixes hyperledger-cacti#3586 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> Co-authored-by: Peter Somogyvari <peter.somogyvari@accenture.com>
brunoffmateus
added a commit
to brunoffmateus/blockchain-integration-framework
that referenced
this issue
Oct 28, 2024
Signed-off-by: Bruno Mateus <brumat315@gmail.com> refactor(satp-hermes): gateway container image definition with bundler Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): merge policies type guard example Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> refactor(satp-hermes): type guards for SATP env variables Signed-off-by: Bruno Mateus <brumat315@gmail.com> squash! - peter's fixes for besu connectivity use LAN IP Instead of hardcoded localhost use the LAN IP of machine so that the gateway container can access it too. Why though? Because if you tell the gateway container that it should access the besu ledger via localhost then it will try to do that through the container's own localhost, which is different from the host machine's localhost (where the besu ledger is actually running). Using the actual IP address of the host machine's primary network interface resolves the ambiguity between the two differnet localhosts. Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> fix(besu): deployContractSolBytecodeNoKeychainV1 requires keychainId In the DeployContractSolidityBytecodeNoKeychainV1Request of `packages/cactus-plugin-ledger-connector-besu/src/main/json/openapi.tpl.json` there are parameters that are required despite the entire point of this operation is to not need them (e.g. keychainId and contract JSON object). Fixes hyperledger-cacti#3586 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com> Co-authored-by: Peter Somogyvari <peter.somogyvari@accenture.com>
zondervancalvez
pushed a commit
to zondervancalvez/cactus
that referenced
this issue
Oct 29, 2024
In the DeployContractSolidityBytecodeNoKeychainV1Request of `packages/cactus-plugin-ledger-connector-besu/src/main/json/openapi.tpl.json` there are parameters that are required despite the entire point of this operation is to not need them (e.g. keychainId and contract JSON object). Fixes hyperledger-cacti#3586 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
In the
DeployContractSolidityBytecodeNoKeychainV1Request
ofpackages/cactus-plugin-ledger-connector-besu/src/main/json/openapi.tpl.json
there are parameters that are required despite the entire point of this operation is to not need them (e.g. keychainId and contract JSON object).Acceptance Criteria
required
The text was updated successfully, but these errors were encountered: