-
Notifications
You must be signed in to change notification settings - Fork 17
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(stellar): add deployment script for testing #428
base: main
Are you sure you want to change the base?
Conversation
+ adjust some values in utils.js to enable it to work with httpcalls
the docker container seems to already start the network (port 8000 is taken), so remove that step from the pipeline
it makes a head request which doesn't work (for some reason). curl -i works, curl -I does not
+ resolve conflict
eventually `generate` will not fund by default, so do it manually + depend on the faucet to do so
echo "STELLAR_ADDRESS=${STELLAR_ADDRESS}" >> $GITHUB_ENV | ||
|
||
- name: Fund Stellar wallet | ||
run: node stellar/faucet --recipient $STELLAR_ADDRESS |
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.
Why don't we just use --fund
parameter to fund the stellar wallet?
You can test it with
stellar keys generate --global test10 --network testnet --fund
stellar keys address test10
and go to stellar.expert and check the balance of the wallet address.
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.
it is possible to fund it during wallet creation but I was thinking that this would act like a test for the faucet
command.
- name: generate operators bindings | ||
run: | | ||
CONTRACT=axelar_operators | ||
node stellar/generate-bindings.js --wasm-path $WASM_DIR/$CONTRACT.optimized.wasm --contract-id $(jq .chains.stellar.contracts.$CONTRACT.address axelar-chains-config/info/local.json) --output-dir ./stellar/bindings/$CONTRACT |
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.
generate bindings script is not working properly as of now. did you run it sucessfully?
closes AXE-5754
Summary
test-sui.yaml
. It executes the things that can be done via thestellar/*.js
files.approve
undergateway.js
execute
underoperators.js
refund
won't work due to a missing gas service contract--estimate-cost
for the operators contract currently doesn't work:allowHttp
needed to be specified in various locations throughout thejs
files.STANDALONE
is correct, notSANDBOX
)stellar-cli
binary because the compilation process was very long. tried usingcargo binstall
to avoid thewget
+curl
business, but there appears to be some upstream issue:note: the wallet step can't be setup immediately after spinning up the network, otherwise you encounter timing errors