-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Add WorkflowRegistry to config #15280
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -279,6 +279,11 @@ Address = '' | |
NetworkID = 'evm' | ||
ChainID = '1' | ||
|
||
[Capabilities.WorkflowRegistry] | ||
Address = '' | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @cedric-cordenier, does config- There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It just means that all values have been set explicitly |
||
NetworkID = 'evm' | ||
ChainID = '1' | ||
|
||
[Capabilities.GatewayConnector] | ||
ChainIDForNodeKey = '11155111' | ||
NodeAddress = '0x68902d681c28119f9b2531473a417088bf008e59' | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1213,6 +1213,33 @@ ListenAddresses = ['1.2.3.4:9999', '[a52d:0:a88:1274::abcd]:1337'] # Example | |
ListenAddresses is the addresses the peer will listen to on the network in `host:port` form as accepted by `net.Listen()`, | ||
but the host and port must be fully specified and cannot be empty. You can specify `0.0.0.0` (IPv4) or `::` (IPv6) to listen on all interfaces, but that is not recommended. | ||
|
||
## Capabilities.WorkflowRegistry | ||
```toml | ||
[Capabilities.WorkflowRegistry] | ||
Address = '0x0' # Example | ||
NetworkID = 'evm' # Default | ||
ChainID = '1' # Default | ||
``` | ||
|
||
|
||
### Address | ||
```toml | ||
Address = '0x0' # Example | ||
``` | ||
Address is the address for the workflow registry contract. | ||
|
||
### NetworkID | ||
```toml | ||
NetworkID = 'evm' # Default | ||
``` | ||
NetworkID identifies the target network where the remote registry is located. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Could you list the other examples of the NetworkID values here as well? |
||
|
||
### ChainID | ||
```toml | ||
ChainID = '1' # Default | ||
``` | ||
ChainID identifies the target chain id where the remote registry is located. | ||
|
||
## Capabilities.ExternalRegistry | ||
```toml | ||
[Capabilities.ExternalRegistry] | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would an unset or empty field invalidate the node's config on boot if the
WorkflowRegistry
is defined in the config but is missing a field or value?Please reflect it (the invalid configuration) in your
test data/scripts
by showing what would be an invalid way of setting the config.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, these are optional values so they can be unset.