-
Notifications
You must be signed in to change notification settings - Fork 2k
[PLEX - 2742] - local cre + simple latest block e2e test #23015
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
base: develop
Are you sure you want to change the base?
Changes from all commits
d067db2
c084cca
41a78fe
9363e81
29ff2fe
b0140b8
de09d17
eaf501e
96d002f
cce9704
e5fd134
b41ade8
d7bd53c
7624cf0
b98b8b1
11d783b
5ccf32f
788e081
626ab3c
637edb3
6669887
05390f0
be358a5
3acba92
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 |
|---|---|---|
| @@ -0,0 +1,82 @@ | ||
| # Same as workflow-gateway-don.toml but with a Stellar chain and the Stellar chain capability (READ path). | ||
| # Anvil 1337: registry and gateway. Stellar: local stellar/quickstart standalone network. | ||
| # chain_id is the STELLAR_LOCALNET network id (SHA-256 of the standalone passphrase), | ||
| # which maps to chain selector 17301180955411967724 in chain-selectors. | ||
|
|
||
| [chip_router] | ||
| image = "local-cre-chip-router:v1.0.1" | ||
|
|
||
| [[blockchains]] | ||
| type = "anvil" | ||
| chain_id = "1337" | ||
| container_name = "anvil-1337" | ||
| docker_cmd_params = ["-b", "0.5", "--mixed-mining"] | ||
|
|
||
| [[blockchains]] | ||
| type = "stellar" | ||
| chain_id = "baefd734b8d3e48472cff83912375fedbc7573701912fe308af730180f97d74a" | ||
|
|
||
| [jd] | ||
| csa_encryption_key = "d1093c0060d50a3c89c189b2e485da5a3ce57f3dcb38ab7e2c0d5f0bb2314a44" | ||
| # change to your version | ||
| image = "job-distributor:0.28.0" | ||
|
|
||
| [infra] | ||
| # either "docker" or "kubernetes" | ||
| type = "docker" | ||
|
|
||
| [[nodesets]] | ||
| nodes = 4 | ||
|
ilija42 marked this conversation as resolved.
|
||
| name = "workflow" | ||
| don_family = "test-don-family" | ||
| don_types = ["workflow"] | ||
| override_mode = "all" | ||
| http_port_range_start = 10100 | ||
|
|
||
| # Keep the registry chain (1337) in node TOML; the workflow stack still needs the EVM registry chain. | ||
| supported_evm_chains = [1337] | ||
| # Stellar chains this DON supports (string network ids), used for key generation and node relayer config. | ||
| supported_stellar_chains = ["baefd734b8d3e48472cff83912375fedbc7573701912fe308af730180f97d74a"] | ||
|
Contributor
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.
I do wonder whether stellar chainID should be handled like that or taken from capability expressed as |
||
| # Workflow runtime limits need both the EVM registry chain (1337) and the Stellar chain selector. | ||
| env_vars = { CL_CRE_SETTINGS_DEFAULT = '{"PerWorkflow":{"CapabilityCallTimeout":"5m0s","ChainAllowed":{"Default":"false","Values":{"1337":"true","17301180955411967724":"true"}},"ExecutionTimestampsEnabled":"true"}}' } | ||
| capabilities = ["cron", "consensus", "stellar", "don-time"] | ||
| registry_based_launch_allowlist = ["cron-trigger@1.0.0"] | ||
|
|
||
| [nodesets.db] | ||
| image = "postgres:12.0" | ||
| port = 13000 | ||
|
|
||
| [[nodesets.node_specs]] | ||
| roles = ["plugin"] | ||
| [nodesets.node_specs.node] | ||
| docker_ctx = "../../../.." | ||
| docker_file = "core/chainlink.Dockerfile" | ||
| docker_build_args = { "CL_IS_PROD_BUILD" = "false" } | ||
| # image = "chainlink-tmp:latest" | ||
| user_config_overrides = "" | ||
|
|
||
| [[nodesets]] | ||
| nodes = 1 | ||
| name = "bootstrap-gateway" | ||
| don_family = "test-don-family" | ||
| don_types = ["bootstrap", "gateway"] | ||
| override_mode = "each" | ||
| http_port_range_start = 10300 | ||
|
|
||
| supported_evm_chains = [1337] | ||
|
|
||
| [nodesets.db] | ||
| image = "postgres:12.0" | ||
| port = 13200 | ||
|
|
||
| [[nodesets.node_specs]] | ||
| roles = ["bootstrap", "gateway"] | ||
| [nodesets.node_specs.node] | ||
| docker_ctx = "../../../.." | ||
| docker_file = "core/chainlink.Dockerfile" | ||
| docker_build_args = { "CL_IS_PROD_BUILD" = "false" } | ||
| # 5002 is the web API capabilities port for incoming requests | ||
| # 15002 is the vault port for incoming requests | ||
| custom_ports = ["5002:5002", "15002:15002"] | ||
| # image = "chainlink-tmp:latest" | ||
| user_config_overrides = "" | ||
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.
When a developer runs
go run . env setupfrom a clean Docker cache, this now only builds/pullsjob-distributor:0.28.0, but the CRE TOML files still ask the environment to startjob-distributor:0.22.1(for example the newworkflow-gateway-don-stellar.tomldoes so). The environment startup path checks thatin.JD.Imageexists locally and tells users to run setup, so setup no longer prepares the image thatenv restartvalidates and the local CRE start fails unless the old tag happens to be cached; either update the configs to 0.28.0 or tag/pull 0.22.1 as part of setup.Useful? React with 👍 / 👎.